Common Reasons For iOS App Rejections
Getting your mobile application affirmed by the gateway rules of Apple can be complicated. All together for an application to make it into the App Store, it must experience an endorsement procedure.
Making an iOS application is an enormous accomplishment in numerous respects. It takes a lot of specialized skill to arrive and for an application to get dismissed after the entirety of that difficult work is past frustrating. Apple has representatives who audit every single application to guarantee quality before they go onto the marketplace. The explanation is to guarantee the nature of applications and to permit clients to get the most ideal experience. All things considered, Apple is all about client experience.
Here are the top most common reasons that cause apps to get rejected to help you better prepare your apps before submitting them for review. More than 40% of applications are rejected due to Guideline 2.1.
They can be divided into 2 categories: metadata rejections and binary rejections
1. Metadata Rejected
If your app has to be rejected by Apple, a metadata rejection is the best case scenario!
This means that the review has only just been interrupted and can be resumed once you provide the missing information.
The most common metadata errors are:
▪ Inaccurate Screenshots
App Store screenshots should accurately communicate your app’s value and functionality. Use text and overlay images to highlight your app’s user experience, not obscure it. Make sure app UI and product images match the corresponding device type in App Store Connect. This helps users understand your app and makes for a positive App Store experience.
▪ Incomplete Information
Enter all of the details needed to review your app in the App Review Information section of App Store Connect. If some features require signing in, provide a valid demo account username and password. If there are special configurations to set, include the specifics. If features require an environment that is hard to replicate or require specific hardware, be prepared to provide a demo video or the hardware. Also, please make sure your contact information is complete and up-to-date.
▪ Misleading Users
Your app must perform as advertised and should not give users the impression the app is something it is not. If your app appears to promise certain features and functionalities, it needs to deliver.
▪ Not Enough Lasting Value
If your app doesn’t offer much functionality or content or only applies to a small niche market, it may not be approved. Before creating your app, take a look at the apps in your category on the App Store and consider how you can provide an even better user experience.
How to Make a Comeback?
If metadata rejected, as we said before, it’s the easiest comeback.
In this case, you will not need to upload a new binary (.ipa file) once you are done making the changes. Simply resume the submission process where it was interrupted.
▪ Screenshots: you have 3 different sizes for your screenshots: 5.5″, 6.5″ and 12.9″. They allow all your screenshots to adapt to the different Apple mobile screens (iPad and iPad Pro included). They must be actual screenshots of your app. Use them to highlight the best features. They are the visual window of your app.
▪ Demo login account: You must provide a valid demo account that the Apple reviewer will be able to use. Showing a simple login screen is not enough.
2. Binary Rejected
An app is a combination of appealing design and super active functions. If your app justifies the defined purpose and solves users’ problems in effective ways, it’s perfect. But if not, your app can be counted poor in performance. And if your app has been “binary” rejected, a little more work will be required for you to make a comeback.
The most common binary errors are:
▪ Crashes and Bugs
You should submit your app for review only when it is complete and ready to be published. Make sure to thoroughly test your app on devices running the latest software and fix all bugs before submitting it.
▪ Broken Links
All links in your app must be functional. A link to user support with up-to-date contact information and a link to your privacy policy is required for all apps.
▪ Placeholder Content
Finalize all images and text in your app before sending it in for review. Apps that are still in progress and contain placeholder content are not ready to be distributed and cannot be approved.
▪ Requesting Permission
When requesting permission to access user or usage data, you should clearly and completely describe how your app will use the data. Including an example can help users understand why your app is requesting access to their personal information.
If your app’s code references one or more APIs that access sensitive user data, the app’s Info.plist file should contain a $!{infoPlistKey} key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting spring 2019, all apps submitted to the App Store that access user data will be required to include a purpose string.
For more information on this please check this.
▪ Web Clippings, Content Aggregators, or A Collection of Links
Your app should be engaging and useful, and make the most of the features unique to iOS. Websites served in an iOS app, web content that is not formatted for iOS, and limited web interactions do not make a quality app.
▪ Repeated Submission of Similar Apps
Submitting several apps that are essentially the same ties up the App Review process and risks the rejection of your apps. Improve your review experience — and the experience of your future users — by thoughtfully combining your apps into one.
How to Make a Comeback?
Even though this is a longer process than a metadata rejection, it is not the end of the world. You can submit your app again after making the necessary adjustments. This second time around, be thorough with your work.
- Really understand the reasons for your rejection. You will receive an email from Apple but the exact reason is not included.
- Contact the Apple Resolution Center for more details and keep the discussion open with them
There is a reason why Apple is so strict with their review process. It gives the ecosystem of the App Store very high-quality standards and therefore remains trusted by iOS users.
To avoid the hassle and waiting period of a second review, best is to follow not only their guidelines but our tips to prevent your app of being rejected 😉
