Swift Auth SDK & Sign in with Apple Refresh Tokens
I've been going through implementing the token revocation for Sign in with Apple users when they manually delete their accounts from within my app (with accounts being created via Supabase Auth). I've created the necessary Edge Functions to accomplish this, but I'm having a hard time finding the correct accessToken & refreshToken from Apple in the Supabase Swift Auth SDK. It seems like when the Apple ID login session is created, the provider access tokens & refresh tokens are left as nil and the session's refresh and access tokens are actually for the new Supabase account (and so are rightly rejected by Apple when sent to them). I also don't seem to see where in the Supabase database the Apple ID's access tokens & refresh tokens are being stored in the auth table (I'm currently on a Free plan, so please let me know if this is possible to view but missing cause I haven't upgraded to Pro yet). I've also reviewed this very helpful thread, but it seems like with the Swift Auth SDK, the values are not the same as the SDK mentioned by the author in this post: https://github.com/supabase/auth/issues/1308#issuecomment-2752190623
Any help would be appreciated! Without it, it seems my only option would be to have users log in to their Apple ID again on Delete Account and use the one-time authorization code there to get new access tokens & refresh tokens so I can invalidate them, but that seems incredibly wasteful and a suboptimal user experience as Supabase should have the provider's refresh token somewhere.
Any help would be appreciated! Without it, it seems my only option would be to have users log in to their Apple ID again on Delete Account and use the one-time authorization code there to get new access tokens & refresh tokens so I can invalidate them, but that seems incredibly wasteful and a suboptimal user experience as Supabase should have the provider's refresh token somewhere.
GitHub
Bug report I confirm this is a bug with Supabase, not with my own application. I confirm I have searched the Docs, GitHub Discussions, and Discord. Describe the bug Apple insists on an in-app optio...
