appstore-approval

Can we resubmit the app after metadata rejection due to invalid demo account details to avoid adding back into the review queue and restart the review clock. As Per this Link An Easy Mistake with iTunes Connect & Metadata Rejections suggested "Do not click “Submit for Review” after getting a Metadata Rejection" to avoid review process. But apple has suggested To provide demo account information: Log in to iTunes Connect Click on “My Apps” Select your app Scroll down to “App Review Information” Provide information in “Demo Account” and/or “Notes” as appropriate Click Save Click Submit for

(See MAIN THRUST below to skip to the main thrust of my question.) My iOS app was rejected in the Apple review process for a minor reason that was easy to fix. However, I wanted to give the new build a once-over testing, including retesting our in-app purchase (there is only a single purchasable item in the app). And now the app crashes when doing the initial retrieval of the product information. It never crashed in this way before, and the code hasn't changed since we successfully tested the in-app purchase in sandbox mode many times. (In fact, no code changed at all between the initially

I've recently submitted my game to the App Store. It has recently been approved and is "Processing for the App Store". When I click on my application, it says "Routing App Coverage File". Just curious on what this means exactly? The "Routing App Coverage File" is a GeoJSON file which describes the coverage area for a public transit routing application (to be used with iOS 6 Maps). The iTunes Connect Developers Guide says: Routing app coverage files are .geojson files which specify the geographic regions supported by your app. The file can have only one MultiPolygon element. MultiPolygon

Many companies rely on white labeled apps to provide their services in a more personal way to their customers. With a few adjustments we can set a logo and a splash screen and even pre-configure our app to our customer needs which has a great impact in their end user experience. Without this my users would need to use the app skipping a lot of configuration steps that in a generic app wouldn't be possible to skip. According to apple: "Apps created from a commercialized template or app generation service will be rejected" Now what can we do to to work around this? Today I saw 4 apps being

My app is a photo-sharing app based on Facebook, and Facebook is the only option for register and login, but my app got rejected with following message: 17.2: Apps that require users to share personal information, such as email address and date of birth, in order to function will be rejected: We found that your app uses Facebook login for authentication purposes only - but does not include any account-based features offered by that site. This is not in compliance with the App Store Review Guidelines. It would be appropriate to modify your app to include account-based features of that social

I am using a custom UIAlertView with UITextField to get password from the user. I have been told that this custom view may cause my App to get reject by Apple; is that correct? If so, what is the appropriate replacement for my custom control? You can add a textfield to your UIAlertView UIAlertView *alertView = [[UIAlertView alloc] initWithTitle:@"title" message:@"msg" delegate:self cancelButtonTitle:@"Cancel" otherButtonTitles:nil]; UITextField *txtField = [[UITextField alloc] initWithFrame:CGRectMake(12.0, 45.0, 260.0, 25.0)]; [alertView addSubview:txtField]; [alertView show]; [alertView