5.1.1

My app was rejected because I use the word 'Enable' on a button, which triggers the system permissions request. I've attached below the the rejection reason, along with the screenshot they provided. I made an appeal for this rejection last week, but haven't heard anything since. So I thought I'd ask for opinions. My issue with the rejection is that not only can I not find any violation of Privacy guidelines, but the suggestion from the reviewer is worse and would be a confusing UX. My flow is a typical onboarding flow, describing features and asking for permissions up-front to ensure the app works properly from the start - something lots of apps do. Sure it could be improved but this is the first version & release. Does anyone have any thoughts on this issue, or even a better suggestion than the one the reviewer provided?

We'll be releasing a B2B app next year, this app will be used as part of the employees job. In guidelines section 5.1.1 (V) If your app doesn’t include significant account-based features, let people use it without a login. If your app supports account creation, you must also offer account deletion within the app. A user does not create an account through the app. An account is created for every employee by the client. A user will login via their employee id. This account is controlled by the client. Any and all data generated by the employee is owned by the client as its business data and data must be linked against whoever created (eg to pay commission to employees for the sales they made) So an account exists but the guidelines say If your app supports account creation, you must also offer account deletion within the app. Since a user cannot create an account themselves, the account deletion requirement isn't relevant here. Is my understanding of the guidelines correct? Or is there another section

Hi, My app was rejected by IOS, based on Guideline 5.1.1: we still find the permission request for camera and photos is not sufficient. To resolve this issue, it would be appropriate to revise these and ensure that they sufficiently explain why the app needs this access. It was my 2nd time already, I am frustrated. I asked IOS to give suggestion and it refuses. Can anyone help me if I modified my message as below: AppName would like to access your Camera Allow AppName to take your photo as profile picture. And this photo will be used in-app messaging only. AppName would like to access your Photos Library Allow AppName to capture image from your Photo Library. This image will used as your profile picture and for in-app messaging only. Thanks your help in advance

Hi, My app was rejected by IOS, based on Guideline 5.1.1: we still find the permission request for camera and photos is not sufficient. To resolve this issue, it would be appropriate to revise these and ensure that they sufficiently explain why the app needs this access. It was my 2nd time already, I am frustrated. I asked IOS to give suggestion and it refuses. Can anyone help me if I modified my message as below: AppName would like to access your Camera. Allow AppName to take your photo as profile picture. And this photo will be used in-app messaging only. AppName would like to access your Photos Library. Allow AppName to capture image from your Photo Library. This image will used as your profile picture and for in-app messaging only. Thanks your help in advance

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?

Good afternoon, I wanted to comment something to see if you can help me find a solution. The apple review team tells us the following “Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage We noticed that your app requires users to register with personal information to purchase in-app purchase products that are not account based” To use our applications you have to buy them but we want users to be able to try it for free for a few days before buying it. Therefore, to avoid that they can use it during the trial days and then uninstall and reinstall it we have put a register at the beginning. This way when the trial days are over they will only have the option to click on the Unlock button which will take them to the App Store to buy it. But I see that in Apple's Best practices it says: “Delay sign-in for as long as possible. People often abandon apps when they’re forced to sign in before they can do anything useful. To help avoid this situation, give people a chance to get a sense of what yo

5.1.1: Apps that facilitate the legal sale of cannabis must be geo-restricted to the corresponding legal jurisdiction. I want to launch a Hemp cannabis delivery service in texas. Delta 8 cannabis is legal in texas, as its derivered from hemp and less than 0.3 percent THC. This leaves me with the question of whether or not it would follow the ios store guidelines if it was geofenced to TX.

Our app is multi-platform android/web/ios, all platforms got their own payment mechanism, on iOS before buying subscription we are asking user to login to check whether they already bought subscription through any other platform so that user don't need to pay twice also to sync purchase with our server. But apple keep rejecting our app with below message. Need help guy. Apple's Message Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage We noticed that your app requires users to register with personal information to purchase in-app purchase products that are not account based. Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the user. User registration that requires the sharing of personal information must be optional or tied to account-specific functionality. To resolve this issue, please revise your app to not require users to register before purchasing in-app purchase products that are not account based.

Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage We noticed that your app requires users to register with personal information to purchase in-app purchase products that are not account based. Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the user. User registration that requires the sharing of personal information must be optional or tied to account-specific functionality. Next Steps To resolve this issue, please revise your app to not require users to register before purchasing in-app purchase products that are not account based. You may explain to the user that registering will enable them to access the purchased content from any of their iOS devices and provide them a way to register at any time, if they wish to later extend access to additional devices. Please note that although App Store Review Guideline 3.1.2 requires an app to make subscription content available to all the iOS devices owned by a

We are currently developing a new iOS application, and we plan to use Sign in with Apple for user authentication. We have a few questions related to this. We understand that Sign in with Apple is compliant with OpenID Connect. However, in our service, the use cases for access_token and refresh_token are limited. Therefore, even if we do not use these tokens, is there a possibility that we will receive a rejection in the Apple Store Review process? Specifically, we are thinking of saving the user's identifier, which can be obtained at the time of authentication, on our server and using it to identify the user. ASAuthorizationAppleIDCredential According to Apple's guidelines (5.1.1 Data Collection and Storage), we need to invalidate the user's tokens when the account is deleted. Does this requirement apply even if the token has already expired? App Store Review Guidelines 5.1.1 Revoke tokens Thank you in advance for your help!

SafariViewController must be used to visibly present information to users; the controller may not be hidden or obscured by other views or layers. I am not clear on what this is addressing. If an app has a link to the company's FAQ page on its website, is this page required to show up in the SFViewController? What if it showed up on the Safari web browser instead?

I've been working for several days to prepare my app for beta testing and to get reviewed by Apple. However, I've encountered a persistent issue. When attempting to transfer my app through the Transfer App, the app icon does not appear, and even when it does transfer, it only appears to load briefly on the App Store Connect site before disappearing. Furthermore, when attempting to upload the same build again, I receive a message indicating that I have already uploaded that build. I am feeling frustrated and unsure how to proceed. Can you please provide some guidance? Thank you. MacBook Pro Apple M2 Pro Ventura 13.2.1 Unreal Engine 5.1.1