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

According to recent update of apple review guideline starting from January 31, 2022: all apps that allow for account creation must also allow users to initiate deletion of their account from within the app Our app currently allow to initiate the deletion process within an app, although user is redirected to the web page, where she needs to confirm it in order to make it happen. The web part of process is conducted in the SFSafariViewController, which is still a part of the app, so here is the question, is this enough to meet review guidelines criteria?

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？

There was a notice in the App Store Guidelines that the account deletion function must be installed by January 31st of next year. However, I would like to know the following to reduce the risk of delaying release dates due to app rejection due to this issue. The standards in the guidelines are ambiguous, so we cannot be sure that our services meet those standards. I would like to know: A) Can the app delete function be provided on the web for mobile? (* Our service provides both in-app web view and mobile browser. ) B) When deleting an account, must all information be deleted? C) Is the name Account deletion important? We provide a function called Withdrawal of Membership, which provides the ability to deactivate account and separate information for a certain period of time and then remove it. There are cases where the customer restores the service. Any help would be appreciated.

Our app you you must sign up by talking with somebody on the phone or via our web site to get a login. You cannot just download our app from app store fully create an account via our app directly. Do we still need to provide delete account mechanism in our app as stated in Apple guideline: https://developer.apple.com/app-store/review/guidelines/#5.1.1 ?

Regarding, all apps that allow for account creation must also allow users to initiate deletion of their account from within the app. If the app has a Create Account link that opens in Safari where the account is created (i.e. outside the app), is the app still considered to allow for account creation and therefore required to allow for account deletion per the new requirement being enforced?

App Store Review Guidelines 5.1.1 If the app supports account creation, it must also provide the ability to delete accounts within the app. I would like to ask you about the meaning of account deletion of the item. In the case of a financial institution (bank), we ask if it can be interpreted as account termination and cancellation of electronic finance (banking app). thank you.

My app has started experiencing intermittent crashes for ios15 devices only. From the logs, the suspected region of crash involves realm threads for write or read or update and TableView reload. But Since the issue is pretty intermittent we are not able to pinpoint the cause of the crash? Does anyone have any suggestion to pinpoint the cause of the crash or what new update in ios15 would have led to this issue.? Below is the Crash Log. From the Crash Analytics. Fatal Exception: NSInvalidArgumentException 0 CoreFoundation 0x9904c __exceptionPreprocess 1 libobjc.A.dylib 0x15f54 objc_exception_throw 2 CoreFoundation 0x176014 +[NSObject(NSObject) _copyDescription] 3 UIKitCore 0xf695a0 -[UIResponder doesNotRecognizeSelector:] 4 CoreFoundation 0x2e474 ___forwarding___ 5 CoreFoundation 0x2d5b0 _CF_forwarding_prep_0 6 UIKitCore 0x3eee54 -[UIUndoGestureInteraction didMoveToView:] 7 UIKitCore 0x194d8c _setInteractionView 8 UIKitCore 0x2f91e4 -[UIView(Dragging) addInteraction:] 9 UIKitCore 0x4a1444 -[UIEditingOverlayVie

If our app doesn't allow in-app account creation, as such we won't be required to offer in app account deletion. Do we have to publish that we don't allow account creation? Is there a button to check to declare that we don't allow account creation in our app?

The new account deletion requirements stated in the app review guidelines (5.1.1(v)) state that: If your app supports account creation, you must also offer account deletion within the app. But what about if the account is owned by a different entity than the user itself, such as for someone using a work account that is owned by their employer? Are we still obligated to offer the employee a way to delete their account within the app?