Regarding Performance - Accurate Metadata i.e. Screenshots in Distribution/Product profile (Guideline 2.3.3): Our e-learning app has been rejected in App Review regarding compliance with Guideline 2.3.3 Performance - Accurate Metadata i.e. Screenshots in Distribution/Product profile. The following is our query: Our app is designed exclusively for iPhone users and will not be distributed for iPad devices. Is it mandatory to include iPad screenshots on the App Store, even if we do not have an iPad version? If not, why is the field requesting iPad App Store screenshots indicated as mandatory? Is this for marketing purposes only? The above query is based on the following instruction provided by the Apple Support/review team: Your iPad Pro (2nd Gen) and 13-inch iPad screenshots show an iPhone device frame scale. Upload new screenshots that accurately reflect the app in use on iPad. Some or all of the provided screenshots do not sufficiently show the app in use. Screenshots should highlight the app's core concept to help users understand the app’s functionality and value. Follow these requirements when adding or updating screenshots: 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 the app's main features and functionality. Confirm that the app looks and behaves identically in all languages and on all supported devices. Make sure that the screenshots show the app in use on the correct device, unless they are included to demonstrate that the app can be used on multiple Apple platforms. For example, iPhone screenshots should be taken on iPhone, not on iPad. Next Steps The iPad Pro (2nd Gen) and 13-inch iPad screenshots show an iPhone device frame. Upload new screenshots that accurately reflect the app in use on each of the supported devices. Looking forward to anyone's kind response that can help us resolve this issue. Thanks!

Regarding Account Deletion (Guideline 5.1.1(v)): Our e-learning app has been rejected in App Review regarding compliance with guideline 5.1.1 (v) Account Deletion. The following is our query: We are including a button that links to the account data deletion request page on our website. This will be placed on the Profile Tab/Page of the app. Will this be sufficient to meet Apple’s guidelines for data deletion requests? The above query is based on the following instruction provided by the Apple Support/review team: The app supports account creation but does not include an option to initiate account deletion. Apps that support account creation must also offer account deletion to give users more control of the data they've shared while using an app. Apps that support account creation must also offer account deletion to give users more control of the data they've shared while using an app. If users need to visit a website to finish deleting their account, include a link directly to the website page where they can complete the process. Follow these requirements when updating an app to support account deletion: Only offering to temporarily deactivate or disable an account is insufficient. If users need to visit a website to finish deleting their account, include a link directly to the website page where they can complete the process. Apps may include confirmation steps to prevent users from accidentally deleting their account. However, only apps in highly-regulated industries may require users to use customer service resources, such as making a phone call or sending an email, to complete account deletion. Next Steps: Update the app to support account deletion. If the app already supports account deletion, reply to App Review in App Store Connect and identify where to locate this feature. If the app is unable to offer account deletion or needs to provide additional customer service flows to facilitate and confirm account deletion, either because the app operates in a highly-regulated industry or for some other reason, reply to App Review in App Store Connect and provide additional information or documentation. For questions regarding legal obligations, check with legal counsel.

Our e-learning app has been rejected in App Review regarding compliance with guideline 4.8.0: Login Services. The following were Apple Support's feedback: The app uses a third-party login service like Google or Facebook, but does not appear to offer an equivalent login option with Sign in with Apple. Next Steps: Revise the app to offer an equivalent login option that meets all of the above requirements. If the app already includes a login option that meets the above requirements, reply to App Review in App Store Connect, identify which login option meets the requirements, and explain why it meets the requirements. Additionally, it would be appropriate to update the screenshots in the app's metadata to accurately reflect the revised app once another login service has been implemented. Note that Sign in with Apple meets the requirements specified in guideline 4.8. Now, regarding their instructions, the following are our queries: Our mobile app for iOS already has SSO login options for Google and Facebook. Could you clarify what is meant by "an equivalent login option"? Are there any specific third-party login services other than "Sign in with Apple" that already comply with the requirements in Guideline 4.8? We are using “Manual sign up/sign in”, “Continue with Google” and “Continue with Facebook” to let users sign up and sign in to our platform. As per the parameters involved with the third-party login, will using sign in with Apple solve the problem related to Guideline 4.8? So is it mandatory under Apple’s Guidelines to include "Sign in with Apple" now, in addition to other SSO options? If it is mandatory, how is it that many iOS apps do not include the "Sign in with Apple" option? From a technical perspective, what options are available to satisfy Apple’s guidelines in this regard? Could manual sign-in/sign-out features of the app cause any conflicts with compliance in this area? Looking forward to anyone's kind response that can help us resolve this issue. Thanks!