When developing an iOS app, it is common to run into unexpected App Store review rejections. A single rejection can easily delay a release by several days.
Below are some of the rejection reasons I have personally run into. They are worth checking in advance if you want to avoid unnecessary review cycles and ship sooner.
Missing In-App Purchase Metadata
If your app uses in-app purchases, the related metadata also needs to be submitted for review. Otherwise, the app can be rejected. This is a very common issue for first-time submitters.
The App Is Too Simple
When SBTI was very popular, I recreated the SBTI test as an app. Apple rejected it because once the user finished the test, there was little reason to keep using the app.
Using Keywords Like Mac or iPhone in Screenshots, Subtitle, or Description
One of my apps needed to work together with software on an iPhone, so I used words like “Mac” in screenshots and phrases like “your iPhone is the best recording device” in the description. That led to repeated review rejections and multiple rounds of revision.
The App Requires Another Device to Work
That same app also required companion software on a Mac. Because of that dependency, the reviewer rejected the submission and asked me to provide a screen recording showing how the app worked so it could be reviewed properly.
Providing an Exit Button Inside the App
This point comes from another developer’s experience, but it is worth noting. Their app included a button to quit the app, and the reviewer interpreted the behavior as if the app had crashed after tapping it. In practice, it is better not to add an explicit exit feature.