User Profile

iOS 14 introduced Account Authentication Modification Extension, that allows "Automatically and transparently convert accounts to Sign in with Apple or to use strong passwords for improved security". We have implemented Account Authentication Modification Extension to support strong password upgrades in our app and it works fine, but there is a little problem. When prompted, one of the two consequent system action sheets is not localised. First action sheet "В этом пароле есть обычное слово - "...", поэтому его легко угадать. iPhone может создать для Вас ..." appears, followed by "The new password will be saved to your iCloud Keychain ...". I guess this to be an iOS bug. Does anyone have the same issue ? Are we missing something in our app ? Is there a workaround or a known bug report ?

Hello, We have registered our outbound domain for use with Private Email Relay Serivice, and it has passed SPF check. We were able to successfully send emails via Private Email Relay Serivice from for example "support@our-domain", but unfotunately emails sent from "noreply@our-domain" via Private Email Relay Service are not being delivered.Is is event possible to use a "noreply" email source with Private Email Relay Service? If so, what could be the possible problem ? Thanks.

Hello,According to the newly refined App Store Review Guidelines (https://developer.apple.com/app-store/review/guidelines/#sign-in-with-apple), apps that use a third-party or social login service to set up or authenticate the user’s primary account with the app are also required to offer Sign in with Apple as an equivalent option. It is also stated that a user’s primary account is the account they establish with the app for the purposes of identifying themselves, signing in, and accessing app’s features and associated services.In our app the only way for a user to set up his primary account is through our own sign up / sign in system. In order to access our app’s primary features, such as posting a listing, accessing messenger, doing any transactions using our internal wallet and others, we require the user to enter his phone number and then verify it through sms. We do not consider users that have not completed this step as fully identified or verified. Therefore when a user signs up or in using also provided by our app third-party social login services (vk.com, facebook.com, ok.ru, google.com), he doesn’t have access to any primary features or any advantages over an unauthorized user.So in this case should we consider providing Sign in with Apple to be optional or still mandatory for our app?