Hey there, We’re implementing sign_in_with_apple package through https://pub.dev › packages › sign_in_with_apple. We’ve been able to follow the link above to configure our application and also set up our apple Service IDs, and redirect url on the apple website Successful use case for login/sign-in: A click on the apple login button should redirect a user to apple’s chrome page on an android phone Here, users should be able to put in their apple email and password in which apple authenticates. After apple authenticates the user, apple sends an authorization code back to the application either as a query or on the json body of the redirect url provided by the application. The authorisation code is then used on our server side to set up a session for the particular user. Our use case: After apples authenticates the user’s email and password after which we don’t get an authorisation code being sent back to our application. We receive “null” instead of an authorisation code. This results in no session being created for the particular user who tries to sign in with Apple What could we be doing wrong?

In the server-side verification link of Sign in Apple ID, we only obtain the public key from the Apple server and verify the JWT validity of the IdentityToken, which is regarded as a successful login. The AuthorizationCode is not further verified and the Token is obtained and saved. However, at present, Apple requires to request the revoke token when deleting the user. We did not hold the Token before. Is there no need to request the revoke token interface when the user deletes the account? Will the APP review fail due to this?

Diagnose errors received by the Sign in with Apple client, or its server infrastructure by identifying the underlying causes of common error codes and explore their potential solutions. View Technote TN3107 >

At the moment I'm busy integrating Sign In with Apple in Zotonic (https://zotonic.com). What I discovered is that access to the REST api end-point can be very unreliable. The development server I use sometimes can't access the end-point for hours because it rejects incoming connections. $ curl https://appleid.apple.com/auth/keys curl: (7) Failed to connect to appleid.apple.com port 443: Connection refused Is this a known issue? How can clients fix this issue? Is there a form they can fill out to unblock their server's ip-address (like microsoft has for delivering mail) Regards, Maas

I cannot find any documentation on this. I would like to know if I should ever worry that my "Sign in with Apple" for my app will stop working due to throttling.

Hello, I am going to make users sign in with apple on my website. This account is my personal account and the real client_id of my company's service is com.ymsco.jangjeon The site url is https://jangjeonhae.bubbleapps.io/ and my redirect uri is https://jangjeonhae.bubbleapps.io/login I have a problem to show the window for sign in with apple. I'm using this https://appleid.apple.com/auth/authorize?response_mode=form_post&response_type=code&client_id=com.ymsco.jangjeon&scope=name%20email&state=[thestate]&redirect_uri=http://jangjeonhae.bubbleapps.io/login/ I got the error "invalid request_ invalid redirect uri" Is there any problem on the link address? Please let me know how to solve the problem.

I am trying to follow the documentation to verify a user in my backend. My App follows the schema that appears in the diagram at the top of the page. I am using npm and: next in frontend (App) express in backend (API Server) Once I receive the token in the API Server from the App, I check it's validity following the steps under the heading Verify the identity token without problem. I have trouble understanding if I am doing enough when I try to follow the stpes in Obtain a refresh token. In this step, I am sent to the page in the documentation to Generate and validate tokens. However, that part of the documentation refers to client tokens, not to user tokens. I can get a new access_token and id_token for the user from my API using the following request: curl -v POST "https://appleid.apple.com/auth/token" \ -H 'content-type: application/x-www-form-urlencoded' \ -d 'client_id=CLIENT_ID' \ -d 'client_secret=CLIENT_SECRET' \ -d 'grant_type=refresh_token' \ -d 'refresh_token=REFRESH_TOKEN' Is this enough to verify the identity? Should I then check that the id_token I receive matches the one I have or is it enough that I have checked the jwt information and validated the refresh_token? Thanks!

Hello, I am working on an OAuth login with Apple for our web applications. We ended up using the npm module "react-apple-signin-auth", which is based off of the apple js library. We are using a popup setup with name and email as requested scopes. This all works perfectly fine on Chrome/Chromium, Mozilla, etc. However, the same code base has issues on Safari browser. We are also having troubles implementing this for our react native Webview. It seems that after the popup is shown (after being manually allowed on the client PC), it frezes after logging in and clicking Continue. It stays with a white screen and does not return back to the origin/redirectURI. I can see someone has a similar issue: https://developer.apple.com/forums/thread/131438 Any clues?

The "Login with Apple" redirects via POST method. I can't store the given token in a session because Symfony resets it if there is a POST request from crossdomains. Is there any way to change the POST method to GET? All other OAuth2 applications are using GET and this works fine with PHP Symfony.

I am sending a post request from my server to get a refresh token after signing in with Apple. https://appleid.apple.com/auth/token The request sometimes succeeds and sometimes times out and I can't figure out why. Specifically, after sending a SYN, there is no SYN/ACK response from the Apple server. What we currently know is that There are cases where it times out and cases where it succeeds. Timeouts do not occur on the local server Why is there no SYN/ACK response? Is there anything else I can try?

Hi Folks, I am bit confused with the auth revoke API behaviour. It will remove Third party app from account or just delete the token so other information is not accessible. Application using apple ID still showing even after revoking using the POST https://appleid.apple.com/auth/revoke. https://appleid.apple.com/account/manage - sign in with Apple, Third party app is still listed. I have used Postman and the after POST Rest API call status was 200. auth revoke API shall remove app from account/manage or not ? Thanks for support.

Does apple sign in private key have expire date

We implemented Sign in with Apple ID in our web app and ServiceId, but The logo is not showing in the “Sign in with Apple” consent screen. Our App is on the store approved. Native Login Can show the App icon but Login with JS and serviceID not working Is there a way to configure this?

I'm trying to implement Sign in with apple My tech stack of frontend include React Native + the Reactjs Problem is that I want to remove the Use a different Apple Id option as shown in the images below 1st one is of Binance which has removed the option that I'm talking about 2nd one is my app where this option is coming I read the full documentation of apple developer but found nothing Kindly help me out

We are trying to adopt social sign in feature with 'sign in with apple'. We thoroughly went through documents and managed to successfully connect to apple sign in page from our website. However, when a user type in the information necessary to sign in, the id_token and the code in the response sent from Apple's server fail to reach our front end server and display 405 Method Not Allowed error. We believe this is the issue with the response_mode in the parameter of the link we use when the button('sign in with apple) is clicked. In our case, response_mode is set to form_post to get id_token and the users' email from scope parameter. It seems the form_post requests using POST method and this is getting blocked by AWS S3 or the CloudFront service that it nests in. We tried to change the way S3 and CloudFront work and let POST method get in but it seems it is not supported. What kind of measures can we take when we really need Apple users' email for sign up and sign in feature? It seems form_post mode is necessary if we want the userinfo we need.

Please, I am implementing sign-in with an apple on an android, but after a successful sign flow, I don't get the authorization code I need to send to the backend server but instead receive an error which says the "405 methods not allowed." I have provided the correct credentials (client_id, redirect_url, and scope) and followed the documentation requirements, but still, I can not get the implementation done. I'll be much appreciated for any support. Thanks.

i have inserted a link of error which is coming after logging in on apple id and the error is "Cannot POST /home" i am using this url for sign in with apple-> "https://appleid.apple.com/auth/authorize?client_id=" + this.apple_clientId + "&redirect_uri="+ this.appleuri + "&response_type=code%20id_token" + "&scope=name%20email" +"&response_mode=form_post" Please help me to correct this error

I received the mail below. Starting June 30, 2022, apps submitted to the App Store that support account creation must also include an option to initiate account deletion. We noticed this app may support account creation. If it already offers account deletion or you’re working to implement it, we appreciate your efforts to follow the App Store Review Guidelines. Apps submitted after June 30 that do not comply with the account deletion requirements in guideline 5.1.1(v) will not pass review. https://appleid.apple.com/auth/revoke However, the revoke api is not working properly. Even if you throw an incorrect key value, 200 is always returned. Is the API working properly? What should I do?

We are not able to retrieve name and, address and ethnicity after using Sign in with Apple. We are able to get email only. May I know where can we get resource to retrieve these information? Please advise.