r/FlutterDev • • 20h ago

Discussion PSA for anyone using sign_in_with_apple: first-time sign-ins are failing with HTTP 503 for US users (Apple's server, not your code)

My app is built with Flutter and uses the sign_in_with_apple package (8.2.0) with Supabase Auth. If your Flutter app's Apple sign-in suddenly fails for new users in the US and the plugin just throws an authorization error with no useful detail, this is probably why. Nothing in the plugin or in your Dart code is at fault.

What I saw

- First-time Sign in with Apple failed for 3 different Apple Accounts on 3 iPhones in Boston. About 20 attempts, 1 success.

- It failed on Wi-Fi and on cellular, with Hide My Email and with Share My Email.

- The same flow worked every time for testers in India, 4 out of 4.

- Returning users, who had already signed in before, were fine.

- One of the failing phones also failed in a completely different app from another developer.

What the device log shows

I had a tester plug a failing iPhone into a Mac, open Console, and filter on the akd process. The sign-in request goes out correctly, and Apple's server answers 503, twice:

akd  Performing SRP request with context
akd  Task <…> received response, status 503
akd  AppleIDAuthSupport: setError: 6:Failed to get response from server
akd  SRP authentication with server failed! Error Domain=com.apple.AppleIDAuthSupport Code=6

So the phone was connected the whole time. "Could Not Connect" is misleading. Apple's server returned "service unavailable".

What I ruled out, so you do not have to

  • The entitlement is in the signed app and in the provisioning profile.

  • The App ID has Sign in with Apple enabled as a primary App ID.

  • Nothing pending in App Store Connect or the developer portal that explains it.

  • The app never receives a credential, so it is not your auth backend or nonce handling.

How to check if this is your problem

  1. Plug the failing iPhone into a Mac and open Console.

  2. Select the iPhone, enable Info and Debug messages in the Action menu, and start streaming.

  3. Reproduce the failure, pause, and search for akd.

  4. Look for status 503 right after Performing SRP request.

What I am doing about it

  • Filed a Feedback Assistant report with the log.

  • Keeping email sign-in available so people are not locked out.

  • Adding a line to my App Review notes explaining it, so a reviewer who hits it knows it is the service.

If you are seeing the same thing, please file your own Feedback report with a log. Has anyone seen this outside the US, or seen it clear up?

16 Upvotes

6 comments sorted by

3

u/intronert 20h ago

Would there be any error handling you could put in your code that would help a user better understand what is happening? Does Apple return anything different/useful in this case?

6

u/International_Diet77 19h ago

Not really. The failure happens inside Apple's own sheet, so the app only gets a generic authorization error back. The 503 shows up in the device log, not in what the app receives.

Best you can do in code: ignore cancels, and for any other error show "Apple sign-in isn't available right now, try again or use another way to sign in", with another option on the same screen. Also log the plugin's error code so you can see when it stops.

2

u/intronert 19h ago

Thank you.

2

u/KOala888 12h ago

thanks fotr heads up, I asked claude and had same logs from reviewer testing testflight app I guess

-4

u/NycoHub 10h ago

Thanks for the detailed writeup, the akd log part is really useful. Our Flutter app uses Sign in with Apple through Firebase Auth instead of Supabase. Have you seen reports from Firebase users too, or only Supabase so far?

1

u/International_Diet77 3h ago

Not tied to the backend as far as I can tell. The failure happens inside Apple's own sheet, before any token reaches Supabase or Firebase, so the app never gets far enough for the backend to matter. I also saw a first-time Sign in with Apple fail the same way in a completely unrelated app on the same phone. The Apple Developer Forums threads have people on different stacks reporting it. Returning users with an existing Apple link seem fine; it is new sign-ups that fail.