I have submitted an app on Appstore.
The app got rejected and here is the Apple Response
"We discovered one or more bugs in your app when reviewed on iPhone running iOS 9.3.1 on both Wi-Fi and cellular networks.
Specifically, the app loads indefinitely upon launch. Please see the attached screenshots for additional details."
I have tested it in multiple ways as told by Apple but unable to reproduce the issue. Moreover Apple says it "the app loads indefinitely upon launch" well the screen shot they have send is not of launch screen but that is of a view controller which comes after launch screen.
Please guide me to overcome this issue.
It sounds like the tester was confused by the contents of the post-launch view controller. You should provide some guidance to the user on how to use the app once it launches with no data. For example, you might have a UILabel that appears to new users explaining how to start using the app. Effective user onboarding is practically a whole discipline. You can seem some good (and entertaining) analyses of user onboarding processes at https://www.useronboard.com/
Related
A user sent me a screenshot saying that my app no longer works for him when he is offline. It's an alert screen from the App Store indicating that "In order to access the App Store, you have to turn off airplane mode or enable WiFi".
This screen instantly appears over my app when he opens it. The app does use in-app purchases but it is a very old Objective-C based app.
I wasn't able to find any information on how I might eliminate this problem 😔 and would appreciate any hints.
I succeeded implementing the SKStoreReviewController. But when the prompt comes up, the "Submit" button is grey & disabled.
I thought it was because I was in debug mode, but when I ship the app with Ad-Hoc PP the result is the same.
Why?
Apple provides the answer for you right here.
When you call this method in your shipping app and a rating/review
request view is displayed, the system handles the entire process for
you.
Emphasis mine.
To help clarify this some:
When building in Xcode, you will see what the OP shows in the screenshot
When building from a CI solution for release, you will not see anything
When running from TestFlight, you will not see anything
When running from the AppStore, only users who purchased (free or paid) your app will see it up to three times a year
When running from the AppStore, users who obtain your app via Connect promo codes will not see it
Users who disable In-App Ratings & Reviews under iTunes & App Stores in the Settings app will never see these prompts under any condition
Apple spells out point 3 here on the provided link:
When you call this method while your app is still in development mode,
a rating/review request view is always displayed so that you can test
the user interface and experience. However, this method has no effect
when you call it in an app that you distribute using TestFlight.
And for point 5, here is what Apple has to say on it at the provided link:
However, customers aren’t able to rate or review an app that was
downloaded using an iTunes Connect promo code.
So sorry, you can't pad reviews via promo codes ;)
Submit button is disabled in development version and the View doesn't even show up in Test Flight versions.
I succeeded implementing the SKStoreReviewController. But when the prompt comes up, the "Submit" button is grey & disabled.
I thought it was because I was in debug mode, but when I ship the app with Ad-Hoc PP the result is the same.
Why?
Apple provides the answer for you right here.
When you call this method in your shipping app and a rating/review
request view is displayed, the system handles the entire process for
you.
Emphasis mine.
To help clarify this some:
When building in Xcode, you will see what the OP shows in the screenshot
When building from a CI solution for release, you will not see anything
When running from TestFlight, you will not see anything
When running from the AppStore, only users who purchased (free or paid) your app will see it up to three times a year
When running from the AppStore, users who obtain your app via Connect promo codes will not see it
Users who disable In-App Ratings & Reviews under iTunes & App Stores in the Settings app will never see these prompts under any condition
Apple spells out point 3 here on the provided link:
When you call this method while your app is still in development mode,
a rating/review request view is always displayed so that you can test
the user interface and experience. However, this method has no effect
when you call it in an app that you distribute using TestFlight.
And for point 5, here is what Apple has to say on it at the provided link:
However, customers aren’t able to rate or review an app that was
downloaded using an iTunes Connect promo code.
So sorry, you can't pad reviews via promo codes ;)
Submit button is disabled in development version and the View doesn't even show up in Test Flight versions.
My app just got rejected, and the reason was that the Apple Watch Extension was "Booting to White Screen" on Apple Watch. They sent me a screencapture of Apple Watch screen that just has white screen. Not much information.
I honestly have no clue where I went wrong... seeing that the app runs fine on both iPhone and the Simulator.
I don't have an Apple Watch to test this with or any logs on real device to show you although I wish I could give as much information on this question.
I don't have any info I can supply other than the fact that they rejected the app, and app doesn't seem to run on real device.
I don't think it would be a code issue seeing that the First Screen in my app is just a few buttons for menu, without much things happening.
Could anyone give me any insight to how to approach this problem? or has anyone had a similar issue?
Here's the response from Apple.
2.2 Details
We discovered one or more bugs in your app when reviewed on iPhone
running iOS 8.2 on both Wi-Fi and cellular networks.
Specifically, upon review we found the Apple Watch app will boot to
white screen display upon launch.
Next Steps
Please run your app on a device to identify the issue(s), then revise
and resubmit your app for review.
For new apps, uninstall all previous versions of your app from a
device, then install and follow the steps to reproduce the issue(s).
For updates, install the new version as an update to the previous
version, then follow the steps to reproduce the issue(s).
If we misunderstood the intended behavior of your app, please reply to
this message in the Resolution Center to provide information on how
these features were intended to work.
Just in case anyone is wondering or having the same issue... it was really a stupid mistake.
I didn't put the images used for Apple Watch in the correct asset catalog with correct target membership. That's why it was displaying the images correctly on simulator, but not on real Apple Watch, since images weren't embedded within the app.
These kind of things needs to be double-triple checked before submitted to app store because it doesn't show on the simulator.
I'm in the middle of getting my very first iOS app pushed out and have been having some trouble with the review process. The app itself is good, but it was recently rejected as Metadata Rejected for the following reason:
Your iTunes Connect settings indicate that your app serves
advertisements. However, we were unable to locate ads in your app.
The thing though is that when I run the app on simulators and my test device (an iPhone 4S), the test ads are coming through fine and are consistently located on the bottom of each screen. I've made sure to include the iAd framework in the binary and have signed/agreed to the iAd contract, but when I asked for more information, all I got for a response was
Your app is metadata rejected as we have asked where to locate ads in
your binary, as your app uses IDFA.
Has anyone else encountered something like this before? Is there a final step that I'm missing to have the real ads show up for the Reviewing process? All other topics close to this that I've found seem to refer to options that are no longer on iTunes Connect.
After sending them a screen capture showing the test ads being shown, it's suddenly been approved. How very odd...