Apple sign in: BAD ID TOKEN
pradeepb28 opened this issue · comments
We're seeing sometimes constantly and sometimes sporadically when attempting to sign in or sign up using Apple
▿ GoTrue.GoTrueError.api
▿ api: GoTrue.GoTrueError.APIError
- message: nil
- msg: nil
- code: nil
▿ error: Optional("invalid request")
- some: "invalid request"
▿ errorDescription: Optional("Bad ID token")
- some: "Bad ID token"
SDK version: master
Hi @pradeepb28 that error is thrown from the GoTrue server, as long as you're sending the correct values in the request, there is not much we can do on the client.
- Can you double-check you're sending the correct
id_tokenandaccess_tokenon the request? - Also, can you check the project is correctly configured? Make sure you follow the docs: https://supabase.com/docs/guides/auth/social-login/auth-apple?platform=swift
Let me know what the results are, I'll gladly help you further.
Hi @pradeepb28 that error is thrown from the GoTrue server, as long as you're sending the correct values in the request, there is not much we can do on the client.
- Can you double-check you're sending the correct
id_tokenandaccess_tokenon the request?- Also, can you check the project is correctly configured? Make sure you follow the docs: https://supabase.com/docs/guides/auth/social-login/auth-apple?platform=swift
Let me know what the results are, I'll gladly help you further.
We have not changed any of those values on our end other than following that example from that url. Just now checked we;ve not rewritten anything on Apple Sign-In October 2023. The issue seems to be sporadic.
Got it @pradeepb28 I'll check with the backend team to see if they know of any change on their side that could impact this.
@pradeepb28 there was a change in Apple's response for that, which caused this error to be returned.
A fix was rolled out 2 days ago (check this issue), if you are still facing this issue, reach out to https://supabase.help/
Thanks.