Apple Auth: 500: Error getting user profile from external provider

[isaachinman]

Describe the bug

We have recently set up Apple auth with Supabase for both web and mobile. We followed the setup instructions carefully, and Apple authentication works beautifully for most Apple accounts.

However, for a subset of Apple accounts, the auth flow reliably fails every single time. The error output, from Supabase, looks like:

{
  "component": "api",
  "error": "json: invalid use of ,string struct tag, trying to unmarshal unquoted value into *bool",
  "level": "error",
  "method": "POST",
  "msg": "500: Error getting user profile from external provider",
  "path": "/callback",
  "referer": "https://app.mycompany.com/auth/callback",
  "remote_addr": "17.235.152.14",
  "time": "2024-02-08T04:22:07Z",
  "timestamp": "2024-02-08T04:22:07Z"
}

At first I could only reproduce this on my own Apple account, but all other testers experienced no issues, so I assumed it was something related to me being the Apple developer who set up the Apple service ID. However, Apple rejected the app submission because their internal tester faced the same 500.

Moreover, the Apple authentication works perfectly fine on our web app, but crucially, it fails for the exact same subset of accounts. That is to say – this very much looks like a Supabase implementation issue, not a user error.

It looks like there is some data/metadata on a subset of accounts which is arriving in a format that Supabase is not expecting, and is somehow breaking the response parsing.

I have not been able to get any more detailed logs.

We are keen to get this resolved ASAP. I have searched the web high and low, but curiously have not found this error with Supabase+Apple reported anywhere.

[isaachinman]

Possibly related to supabase/auth#1402?

[pingustar]

@isaachinman what is the status of this issue? Have you found a solution? I have the same issue

[isaachinman]

This was indeed the GoTrue issue that I linked, which has now been fixed. This issue can be closed.

[joris-delorme]

I got the same but with LinkedIn Auth...

[kangmingtay]

@joris-delorme linkedin oauth is a different issue - it was a breaking change that wasn't being communicated on linkedin's end :( - we've made a supabase/auth#1536 for it but it will take awhile before we are able to roll it out to everyone on the hosted platform

if you need this urgently, please open a ticket at https://supabase.help/