Skip to content

Instantly share code, notes, and snippets.

@hebbian

hebbian/apple-review-asabri-star-22112022.md

Last active November 22, 2022 14:58
Show Gist options
  • Save hebbian/77b3701d78fb0a3f9f32912e9bd5dd38 to your computer and use it in GitHub Desktop.
Save hebbian/77b3701d78fb0a3f9f32912e9bd5dd38 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
apple-review-asabri-star-22112022.md

Guideline 2.1 - Information Needed

We’re looking forward to continuing our review, but we need more information about your business model and your users to help you find the best distribution option for your app.

Next Steps

Please review the following questions and provide as much detailed information as you can for each question.

  1. Is your app restricted to users who are part of a single company? This may include users of the company's partners, employees, and contractors.

  2. Is your app designed for use by a limited or specific group of companies?

  • If yes, which companies use this app?

  • If not, can any company become a client and utilize this app?

  1. What features in the app, if any, are intended for use by the general public?

  2. How do users obtain an account?

  3. Is there any paid content in the app and if so who pays for it? For example, do users pay for opening an account or using certain features in the app?

Resources

Learn more about app distribution options on Apple Developer.

Guideline 2.1 - Information Needed

We have started your app's review, but we were unable to successfully access all or part of your app. In order for us to continue the review, we need to have a way to verify all app features and functionality. Typically this is done by providing a demo account that has access to all features and functionality in your app.

Next Steps

To resolve this issue, provide a user name and password in the App Review Information section of App Store Connect. It is also acceptable to include a demonstration mode that exhibits your app’s full features and functionality. Note that providing a demo video showing your app in use is not sufficient for us to continue the review.

Resources

To learn more about providing information to App Store Review in App Store Connect, see App Store Connect Help.

Guideline 2.3.3 - Performance - Accurate Metadata

We noticed that your screenshots do not sufficiently show your app in use. Specifically, your 12.9-inch iPad Pro, 6.5-inch iPhone, and 5.5-inch iPhone screenshots do not show the actual app in use in the majority of the screenshots.

To help users understand your app’s functionality and value, your screenshots should highlight your app's core concept. For example, a gaming app should feature screenshots that capture actual gameplay within the app.

Next Steps

Please revise your screenshots to ensure that they accurately reflect the app in use on the supported devices.

Keep in mind the following requirements:

  • Marketing or promotional materials that do not reflect the UI of the app are not appropriate for screenshots.

  • The majority of the screenshots should highlight your app's main features and functionality.

  • Confirm that your app looks and behaves identically in all languages and on all supported devices.

  • Make sure that the screenshots show your app in use on the correct device. For example, iPhone screenshots should be taken on iPhone, not on iPad.

Resources

  • To learn more about creating great screenshots for the App Store, see Optimizing Your App Store Product Page.

  • To learn more about uploading screenshots, see App Store Connect Help.

Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage

We noticed your app encourages or directs users to allow the app to access the location. Specifically, your app directs the user to grant permission in the following way(s):

  • A message asks users to reconsider their decision after they deny permission.

Permission requests give users control of their personal information. It is important to respect their decision about how their data is used.

Next Steps

To resolve this issue, please revise the permission request process in your app to not ask the user to reconsider denying permission.

If necessary, you may provide more information about why you are requesting permission before the request appears. If the user is trying to use a feature in your app that won't function without access to the location, you may include a notification to inform the user and provide a link to the Settings app.

Resources

Learn more about designing appropriate permission requests.

Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage

We noticed that your app requests the user’s consent to access the location, but doesn’t sufficiently explain the use of the location in the purpose string.

To help users make informed decisions about how their data is used, permission request alerts need to explain and include an example of how your app will use the requested information.

Next Steps

Please revise the purpose string in your app’s Info.plist file for the location to explain why your app needs access and include an example of how the user's data will be used.

You can modify your app's Info.plist file using the property list editor in Xcode.

Resources

  • See examples of helpful, informative purpose strings.

  • Review a list of relevant property list keys.

Please see attached screenshots for details.

iOS App 1.0.0App Version Rejection Reasons:

2.1.0 Performance: App Completeness

2.3.3 Performance: Accurate Metadata

5.1.1 Legal: Privacy - Data Collection and Storage

Rejection Attachments:

Screenshot-1121-75926 a.m..png Preview

Screenshot-1121-75931 a.m..png Preview

Screenshot-1121-75942 a.m..png Preview

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment