I am a polyglot seasoned software engineer. Besides the day job, I contribute to open source projects, beta test startup products, and offer consultancy.
I will add a tad more information. When the Apple Sign In was introduced, developers had the option of receiving id_token and code via URL fragment or query, besides form_post on the redirect URL.
But then Apple has changed it. Now, id_token and code are only sent via form_post to the redirect URL.
Another tidbit is that you can get a "Sign in with Apple" button, which conforms to the Apple human interaction guidelines by adding a div with id "appleid-signin". Apple's JS will automatically replace it with a button.
Great write up. Thank you, @aryaminus .
I will add a tad more information. When the Apple Sign In was introduced, developers had the option of receiving
id_token
andcode
via URL fragment or query, besidesform_post
on the redirect URL.But then Apple has changed it. Now,
id_token
andcode
are only sent viaform_post
to the redirect URL.Another tidbit is that you can get a "Sign in with Apple" button, which conforms to the Apple human interaction guidelines by adding a
div
with id"appleid-signin"
. Apple's JS will automatically replace it with a button.Hi how to handle the form_post ?
i try to fetch the redirect URL, but nothing is shown on console