5.1.1

If a product requires an account to be created for a user to use it, and email registration is the only way it can create an account, does this count as a violation of this section 5.1.1(x)? Because if you don't complete registration, you can't use the following features. But the product's features require users to create a unique user ID before they can use it Would it be possible if more than one registration method was provided, such as adding login via Apple ID？

We noticed that your app requests the user’s consent to access the camera, but doesn’t sufficiently explain the use of the camera in the purpose string. To help users make informed decisions about how their data is used, all permission request alerts need to specify how your app will use the requested information. Next Steps Please revise the relevant purpose string in your app’s Info.plist file to specify why your app needs access to the user's camera. Make sure the purpose string includes 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. look it, how to do it ?

Hi everyone, I would like to publish an app that I am rejected because it is account based. I need the user to register for statistical purposes. In addition, the user can comment, like and set favorite content. Is it possible that this is not enough? If your app doesn't include significant account-based features, let people use it without a login. Isn't this enough to be significant? the core of the app is precisely that of collecting statistical data by monitoring the user's position while watching content corresponding to works of art. Isn't a privacy policy enough to explain why the user has to register? I don't want an access without registration. Do you have any suggestions?

This Is the reason that my game was rejected in AppStoreConnect. [ ] I ask users permission but I can't determine what user choose, allow or deny. So question is that How to determine users answer, and if it's DENY, what code I must write so my unity ads do not track that user

**We noticed that your app collects information from various public sources to build individual profiles, which is not appropriate for the App Store. Next Steps To resolve this issue, please remove any feature that attempts to build individual profiles based on collected public data. ** I do not understand what information that I collect from various public sources to build individual profiles My app takes the image from user and process it to extract facial features and compare other faces in the app database also the user can create an account if he wants to post a missing report and I ask to input the name and gender and date of birth and other information of missing person and all of this I explain in app review But I still face this replay what to do ?

Hi, I have an issue with App submission. My flow is: show third party cookie consent banner (is an external SDK) show ATT Apple with this message Allowing tracking will enable more personalized ads for you. Apple says this: You collect data to track after the user selects Ask App Not to Track on the App Tracking Transparency permission request. Specifically, we noticed the app accesses web content you own and collects cookies for tracking after the user asked you not to track them. Next Steps To resolve this issue, please revise the app so that you do not collect data for tracking purposes if the user does not give permission for tracking. Alternatively, if you do not collect cookies for tracking purposes, revise the cookie prompts that appear in the app to clarify you do not track users. in the rejection they put the ATT alert and the third party banner as the screen Do you have any input on this as Apple never says things clearly about what the problem is. Thank you

Issue from App Review: My app shows a custom explanation screen before triggering the system location permission dialog. This screen explains why location access is needed. It includes: A “Continue” button → triggers the system permission dialog A “Not Now” button → dismisses the explanation and delays the permission request Apple states that: “The user should always proceed to the permission request after the message.” They are asking me to remove the exit button from the pre-permission message. My Questions Is it now against policy to include a “Not Now” option in a pre-permission explainer screen? Are we required to immediately show the system permission dialog after any pre-permission explanation? What is the recommended UX pattern if the feature depends on location but I don’t want to force the permission immediately at launch? Would it be compliant to: Remove the “Not Now” button, OR Remove the custom pre-prompt entirely and rely only on the system dialog? The feature in question requires location to fu

We are a development team that has developed an application for an oral and maxillofacial surgery clinic. The developer account from which the application is published is registered to a consulting firm that works with this clinic. We were denied publication due to the fact that the developer's account and its name did not reflect the essence of the application. We opened an individual entrepreneur with the same name as the name of the application, but as a legal entity we are not allowed to register, since it is an individual entrepreneur. Support responds to this question by asking us to register the developer's account as an individual entrepreneur and try to send it for verification, and only then will they give an answer based on the verification results. If we register as a regular individual entrepreneur, will the application be allowed for publication? Has anyone encountered this?

Hello, We have developed an app iOS and Apple reject the second update of app (categorie NEWS) for this motivation: We still noticed that your app requires users to register or log in to access features that are not account-based. Next Steps To resolve this issue, please revise your app to let users freely access your app’s non account-based features. Apps may not require users to enter personal information to function, except when directly relevant to the core functionality of the app or required by law. You should allow users to freely access your app’s non account-based features. For example, an e-commerce app should let users browse store offerings and other features that are not account-based before being asked to register, or a restaurant app should allow users to explore the menu before placing an order. Registration must then only be required for account-specific features, such as saving items for future reference or placing an order. But I would to like answer to Apple with this motivation: The App r