Posts

Post not yet marked as solved
1 Replies
Hi David, Would you mind filing a Feedback Report with the Accounts & AuthKit - https://developer.apple.com/bug-reporting/profiles-and-logs/ Profile? please include a sysdiagnose (after installing the profile) and paste your FB number here so that we can take a look a it. Thank you.
Post not yet marked as solved
3 Replies
Hi, Please verify if this is still happening on the available beta versions for both iOS 14 and iOS 13.6 If you find that the issue remains, please file a feedback as previously asked and past your Feedback ID here so that we can take a look at your specific issue.
Post not yet marked as solved
2 Replies
`realUserStatus` is only available for iOS applications using the Native implementation of Sign in with Apple using the Authentication Services Framework.
Post marked as solved
4 Replies
Hi Alfie,If you request an email address when signing in with Sign in with Apple.The first time a user creates an account with you, the user will be prompted to either share their real email address, or hide it (which will create a unique, random email address so that you can comunicate with the user, without the user sharing his real email address.This random email address will be returned on the email property of the credential.It is important to note that this will only be retreived to you the first time the user signs in to your application, all subsequent login attempts will only return the User identifier to the app and not the email address or name.
Post not yet marked as solved
5 Replies
Hi DavidWhen passing both types of requests, you will get the result in the delegate method (just as you would when you pass only one).If there are existing credentials they will be there in the delegate method where you can get the information depending if you get a PasswordCredential or an AppleIDCredential.If there are no existing credentials, you will receive most likely an error in the delegate method. At this point which most likely will happen on your login screen, the user will have the option to create a credential by clicking on the Sign in with Apple button which should contain the code with only the AppleID request.I would recommend adding the code with both requests when the login view is loaded, so that if there are any credentials, the user can see the prompt and select their credential and move right on to your application.the Single request (AppleID only request) code should be executed when the user selects "Sign in with Apple" with the button.
Post marked as solved
1 Replies
Hi David.Using both a `ASAuthorizationAppleIDProvider Request` and the `ASAuthorizationPasswordProvider Rquest` will try to find an existing credential, either a Sign in with Apple credential or a credential previously stored by the user in their Passwords.It will however not show any UI or prompt the user to create a Sign in with Apple credential if none is found.To present the user the option to create an account using Sign in with Apple, you should only use `ASAuthorizationAppleIDProvider Request` which will check for existing Sign in with Apple credentials and if none is found will prompt the user to create an account.For more information on this, you can check the `Request Existing Credentials` topic on the documentation for Sign in with Apple here.
Post not yet marked as solved
5 Replies
Hi,When using the native API, Having both a password request and an appleID request performs a search for existing credentials (either Apple ID or Password) if none are found the API will not return any credentials.To create a Sign in with Apple credential you need to only pass an AppleID request. this will show the UI and allow the user to create a Sign in with Apple credential with your application.
Post not yet marked as solved
2 Replies
HiUser identifiers are team-scoped, which means that it will be unique to a developer account. Sign in with Apple user identifiers cannot be matched across diferent developer accounts.
Post not yet marked as solved
1 Replies
Hi,The private email is also team-scoped, which means it will remain the same across all your applications.This also means it will not change on subsequent authorizations by the user.
Post not yet marked as solved
3 Replies
`realUserStatus` is a property of the native implementation of Sign in with Apple using the Authentication Services framework.It is not available through Web / JS implementations of Sign in with Apple.
Post not yet marked as solved
3 Replies
Whenever a user signs up to your application for the first time on an iOS device you will get the usual `ASAuthorizationAppleIDCredential` as a result.This `ASAuthorizationAppleIDCredential` contains a property named `realUserStatus` that will contain what you are looking for.You can find more information by looking through this documents:https://developer.apple.com/documentation/authenticationservices/asauthorizationappleidcredential/https://developer.apple.com/documentation/authenticationservices/asuserdetectionstatus?language=objchttps://developer.apple.com/documentation/authenticationservices/asauthorizationappleidcredential/3175418-realuserstatus?language=objc