5.1.1

This is a massive clause change and it doesn't seem like enough people are discussing this as the update to the the anti-steering clause is the hotter topic (with everyone forgetting that its no longer of any benefit to them if users don't give you their email addresses anyway). Apps may request basic contact information (such as name and email address) so long as the request is optional for the user, features and services are not conditional on providing the information, and it complies with all other provisions of these guidelines, including limitations on collecting information from kids.” Ok. So now, if my app has account based features, they would need to register. If they register, if we don't use a phone number or email address, we would have to use a unique identifier. So ok, let's use a unique identifier. Now, that user forgets their password. Well, good luck to you, you didn't give us your email or number, so we can't verify that it was you who created the account. Like how Reddit does it. Ecommerce

Hello, My app has gotten rejected because of guideline 5.1.1. My app required an account and a subscription to be used. Can someone please let me know how they were able to get approved? Would adding Apple sign in work? Would letting the user browse the empty app work? They cant of anything without a subscription so I don’t know why this is getting declined. I’ve asked if any of them would comply but the reviewer says they won’t offer any suggestions on app design, when that wasn’t the question. I just wanted to know if anything would make the app comply before I waste my time implementing anything.

Hello Apple. My app rejected with reason - The app must be published under a seller and company name that is associated with the organization or company providing the services. In this case, your app must be published under a seller name and company name that reflects the APPNAME name. My APPNAME diffrent than company name. How can i solve it?

Below is the response we received from app store reviewer -Legal - 5.1.1We noticed that your app uses Facebook login for authentication purposes but does not include account-based features offered by that site.In order to use Facebook for authentication, your app must include significant account-specific functionality from Facebook.Question :What account-specific functionality from Facebook should we implement to fulfill the requirement ?

Apple blocked an update for a personal database app citing the 5.1.1 guideline. The permission alert message (Purpose String) was not changed but the latest update got multiple rejections because of it.### WorkflowUser taps on an Add Picture button, and if the user specify Camera from an action sheet of sources (e.g. Photo Library, Paste from Clipboard), the app then tries to access the camera, and causes iOS to display a permission request alert. ### Permission Request AlertHere is the iOS standard alert **title**:> [AppName] Would Like to Access the CameraThe initially approved developer-supplied **message** (Purpose String):> Camera will be used to take pictures to store in [AppName].-> Rejected.> Camera will be used to take pictures so that you can store them in [AppName].-> Rejected again.We did look at Apple's docs and also asked Apple for recommendations, but they just kept saying that the alert needs *to specify why the app is requesting access to the user's camera.*### Othe