Overview

Once an app has been published you may receive a rejection from Apple on Guideline 2.1 - Performance - App Completeness. This article outlines why this usually happens and presents the steps you can take to resolve it. 

Diagnosis

You will have received a notification that your app has been rejected by Apple because of Guideline 2.1 - Performance - App Completeness. Here is an example of a rejection message: 

This rejection can be related to various reasons. The most common are:

• metadata and binary rejections
  • inaccurate screenshots
  • incomplete information
  • misleading, irrelevant information in the app's description
  • bugs and crashes
  • broken links
  • placeholder content
  • requesting permission even if not needed
  • substandard user interface
• demo account missing. A demo account is required by Apple so that Apple reviewers are able to access some or all parts of your app during their review process. Thus, You received this because Apple was not able to proceed with your app review, since it appears you had set a requirement for users to have an account to access your app. Since Apple had no account to check its functionality, they could not review your app.

Back to top

Solution

Based on the exact error message above you would need to determine how to resolve it by using Technical Note TN2431: App Testing Guide.

To solve Metadata Rejections 

• Verify the screenshots are accurate and follow the Screenshot Tools Best Practises
• If a login would be required for the app to be accessed, ensure that the Sign-in feature is disabled.
• To avoid this rejection while we implement the Sign in Apple functionality gets implemented, we suggest disabling all the third-party and social logins and then re-enable once the app is published. 

To solve Binary Rejections 

• Ensure that the app is tested on multiple iOS devices to ensure that it does not crash or report any bugs.
• All links within the app must work. 
• The app, once live in the App Store must be 100% available with no content missing. 
• The app should only request permissions to device features that it requires, and if requires location services, the app should explain why on initial start-up.
• The app must provide a good user experience and interface. 

To solve problems related to the inexistence of a demo account if you don't use the Group Management Add-on:

1. Access the app's PWA version on your browser.
   • You can replace APPCODE with the app's app code in the following URL to access your PWA app with our Whitelabel domain:
   • https://webapp.mobileappco.org/m/APPCODE
2. If the app's sign-up page opens up, click on "Sign up with email".
   • If the sign-up page doesn't up, click on the gear icon on the top-right of the screen and click on "Sign up or Log in".
3. Use "apple@test.com" as the username/email, "test" as the password, and the account's name.
   • If the app requests the user's birthday, just enter a random date.
4. Once the account is created, Log in to App Store Connect.
5. Click My Apps.
6. Select your app.
7. Click on the app version on the left side of the screen.
8. Scroll down to App Review Information.
9. Check the Sign-in required box, and enter demo credentials in the User name and Password fields. 
   
10. Once you have completed all changes, click Save at the top of the Version Information page. 

To solve problems related to the inexistence of a demo account if you use the Group Management Add-on:

1. Log in to BiznessApps CMS.
2. Navigate to Manage > Customers, and click Add User.
   
3. Enter the account credentials.
   • Email
   • Username - can be called Apple or Demo as an example
   • Password
     
4. Click Next.
5. Select the assigned group, if required. Alternatively, leave as Unassigned. Click Next. 
   
6. Under Feature Access, check the Select All option.
   
7. Log in to App Store Connect.
8. Click My Apps.
9. Select your app.
10. Click on the app version on the left side of the screen.
11. Scroll down to App Review Information.
12. Check the Sign-in required box, and enter demo credentials in the User name and Password fields. 
    
13. Once you have completed all changes, click Save at the top of the Version Information page. 

Back to top

Testing

Once you follow the above recommendations and fix your app you can resubmit it to Apple and check if this time it got accepted.

Your  app should adhere to the following guideline (taken from Apple Guidelines on Performance)

Back to top

Related Articles

• Screenshot Tools Best Practises