5.1.1

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

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?

Hi, Our app (Tenkobo) received a rejection notice after review due to the fact that we use Gemini AI since 3 builds ago. Since then, we have been improving the disclosure of the data we collect, explicitly stating all the data, introducing a new feature that checks granular consent and syncs consent state for the user to the backend, and controls for whether to send to the Gemini API service for that feature depending on consent state for the user. Moreover, this feature is a premium add-on to a module that already does most things locally on the device and sends to our cloud infrastructure to allow storage and sync when users use multiple devices. It is a multi-platform app. However, despite every improvement, we keep getting the same Rejection reason that The issues we identified still need your attention. I have asked for help or even that the rejection reason be more specific, but nothing. I have send pictures, and in this last rejection about 8 hours ago, I had to reply with a video showing that what the

I want to clarify why both email and phone number are mandatory at registration, while still allowing users to log in with either method if one fails. Email Address (Collected at Registration) Account Creation & Verification: We use email to establish a unique, verifiable account for each user. This prevents duplicate or fraudulent profiles. Primary Communications: All booking confirmations, trip updates, support requests, and in-app chat messages between care seekers and carers are sent via email. This ensures users have a reliable record of every transaction and message. Phone Number (Collected at Registration) OTP-Based Security: We send a one-time password (OTP) via SMS during registration and login. This SMS-OTP step is critical to confirm that the user owns the provided phone number and to safeguard against unauthorized account access. Critical Trip Notifications: During a booked trip, carers and care seekers must receive time-sensitive alerts (e.g., gate changes, flight delays, check-in reminders)

Hi everyone, in an email that came to me directly from apple, which refers to the aforementioned guidelines, the following is shown in the figure: Now in my app, the login is done directly on a third IdP, so I wanted to understand if the issue of user cancellation falls into this case or not, since as I said it is a user on a third IdP (ex Google, Microsoft, Private IdP etc.), and therefore the rule only applies to those apps that allow registration directly within it and not on an external IdP. I hope I was clear. Thank you

My app is getting rejected for this reason: Issue Description The app requires users to register or log in to access features that are not account based. Specifically, the app requires users to register before accessing any content. 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. My app does require sign in tho like any social media app and the previous version had been approved no problem. I made an appeal which was rejected for the same reason and I am not getting an answer.