Sign in with Apple: "Sign Up Not Completed" for every App ID in our team — framework returns canceled (1001) with empty userInfo

Sign in with Apple fails for every App ID in our team (K9UFUZF2XW), on every device and every Apple ID we have tried.

The system sheet appears, the user authenticates successfully, the sheet then shows "Sign Up Not Completed", and no credential is returned. The failure happens after authentication — this is not a client-side rejection.

I have spent several days isolating this and have ruled out everything on my side. Posting the full evidence in case an Apple engineer can look at the server-side state for our team, and in case it helps others hitting the same wall.

WHAT THE FRAMEWORK ACTUALLY RETURNS

The client library we use (expo-apple-authentication) discards the original NSError, so I patched its native layer to surface the raw error verbatim. This is what ASAuthorizationController hands back to didCompleteWithError, immediately after the user authenticated and the sheet displayed "Sign Up Not Completed":

ASAuthorizationError .canceled (rawValue = 1001) domain = com.apple.AuthenticationServices.AuthorizationError code = 1001 desc = The operation couldn't be completed. (com.apple.AuthenticationServices.AuthorizationError, error 1001) userInfo: <empty> NSUnderlyingError: <none>

So the framework reports a user cancellation that never happened, with a completely empty userInfo and no underlying error. There is no diagnostic information on the client at all — I cannot debug this any further from my side, because the information does not exist there.

Note: the same failure surfaces as a different error code depending on the client library version — .unknown (1000) with the older version, .canceled (1001) with the current one. The user-visible behaviour ("Sign Up Not Completed") is identical in both. So the error code is not a reliable signal here.

WHAT I RULED OUT

  1. Not the App ID. I created a brand-new App ID (kz.auraai.ios) with Sign in with Apple enabled as a primary App ID, built a fresh binary, tested on the same device with the same Apple ID — identical failure. Two independent App IDs in the same team fail the same way.

  2. Not the entitlement. Verified inside the signed binary, not just in the portal:

application-identifier = K9UFUZF2XW.kz.auraai.ios com.apple.developer.applesignin = ["Default"]

I also tried the workaround suggested elsewhere on these forums (removing the entitlement while keeping the capability in the portal). That made it strictly worse: iOS then rejects the request instantly, without showing the sheet at all. Which confirms iOS reads the entitlement correctly, the sheet works, and the user authenticates — the failure is downstream of all of that.

  1. No stray or wildcard App IDs. A commonly cited cause is other App IDs in the team lacking the entitlement. I enumerated the whole team via the App Store Connect API: it contains exactly two App IDs, both with APPLE_ID_AUTH = PRIMARY_APP_CONSENT. No wildcard identifiers exist.

  2. Not the Apple ID, the device, or the iOS version. The same Apple ID, on the same device, with the same iOS, signs in successfully through another app belonging to a different team (Expo Go, host.exp.Exponent) — a valid identity token is returned. A second, unrelated Apple ID on another device fails in my app in exactly the same way. So this is not scoped to one account: it affects every user of the app.

  3. Agreements and membership are in good standing. Program License Agreement accepted 30 June 2026; Developer Agreement accepted 26 June 2026; membership active.

  4. Both distribution types fail. TestFlight and ad-hoc.

WHAT IS LEFT

After all of the above, the only variable that differs between the working case (a different team's app, same device, same Apple ID) and the failing case (my app) is the Apple Developer team itself.

This exact signature — sheet renders fully, final server submit fails, "Sign Up Not Completed", delegate reports canceled with no userInfo, not reproducible in other apps on the same device — is documented in thread 122458 ("Error: Sign-Up Not Completed"). In that case it affected multiple developers, including Apple's own sample app, and was ultimately resolved by Apple on the server side, with a recurrence reported in June 2025.

THE ASK

Could someone from Apple check the server-side Sign in with Apple registration for team K9UFUZF2XW (App IDs kz.auraai.app and kz.auraai.ios)?

I am not looking for configuration advice — I have exhausted the client side and there is nothing left to configure. This looks like the same server-side state that was fixed in the referenced cases.

Feedback Assistant: FB23716661 (includes sysdiagnose with the Accounts/AuthKit profile, timestamp, and video of the failure).

This is currently blocking us: because Sign in with Apple works for none of our users, guideline 4.8 prevents us from offering Google Sign-In, so we are shipping with email-only login.

Happy to provide the binary, entitlements dump, or a fresh sysdiagnose on request.

RESOLVED - Update from team 3TJ6S8TP4K (app.effable), FB25583750: for us this turned out to be network-path dependent, not the App ID. Same iPhone, same build, same brand-new Apple Account: first-time sign-up failed with "Could Not Connect" on our Wi-Fi and succeeded immediately after switching the phone to cellular. On the failing network the akd log shows the sign-up SRP reply could not be parsed (NSCocoaErrorDomain 3840, kCFPropertyListOldStyleParsingError), i.e. the device got something that wasn't Apple's response, which looks like a stale DNS record or route to the identity servers from that network. Worth trying before anything else: cellular instead of Wi-Fi, a router restart, or a DNS cache flush. Our App Review rejection came from a reviewer device that may be on a similarly affected network; we've asked them to retest on a different connection. This may not explain every case in this thread (ours worked for other users on 08-28, 09-07, 09-08, 09-28, 10-30 and 11-08), but it's a two-minute check.

Same issue on our App ID (registered 19 Oct 2026). "Sign-Up Not Completed" then "Could Not Connect" after Face ID, on Wi-Fi and on mobile data. The same Apple Account signs in to other apps fine, and nothing reaches our server. Worked once on 5 Nov. Filed as FB25588932.

Same issue here: Team ID UKVUVAJ7Y6 (Individual, new since Nov 14 2026), bundle ru.smartkach.ios, Sign In with Apple enabled as primary App ID (re-enabled once, no change). The "Create an account" sheet appears, then "Could Not Connect"; akd logs AKSQLError -6003 "No applications were found with the provided Client ID", the auth server answers HTTP 503, then AKAuthenticationError -7005/-7003. Same in development and TestFlight builds. Filed as FB25593347 (sysdiagnose with Accounts/AuthKit profile attached).

Same issue on our app since around Nov 13, 2026: first-time Sign in with Apple sign-ups fail with "Could Not Connect" / ASAuthorizationError 1000, while users who authorized before can still sign in.
Team ID: ZK478KHNPD
Bundle ID (Client ID): com.majihima.app
Feedback: FB25594048

Possibly the same issue, on a team that received an app transfer.

Team ID: 7F4R94ZBC6
Bundle ID: com.macadam.app (live on the App Store)
Feedback ID: FB25594732

The app was transferred to this team on 2026-09-15. Since 2026-11-14 around 00:00 UTC, the day the 60-day transfer period ended, about half of first-time Sign in with Apple attempts fail on device with ASAuthorizationError 1000. No request reaches our server. Returning users sign in normally.

  • Same build, no release, backend or portal change at that time. It worked for 3 days before.
  • About 2,000 users a day, versus about 80 before. Spread evenly across countries and iOS versions (26.5 to 27.2.1).
  • It looks intermittent per attempt: about 1 in 5 affected users later succeed with Sign in with Apple on a retry.
  • A brand-new Apple ID authorized fine in our test (AuthKit log: SRP succeeded, ec = 0, hsc = 200), so it does not fail every time.
  • Sign in with Apple is enabled as a primary App ID on 7F4R94ZBC6, no grouping.

@Paris X Pinkney, could you check whether our App ID needs the same server-side fix after the transfer?

Same issue here since November 14, 2026. First-time sign-ups fail; users who already authorized the app still sign in.

Team ID: 7U7B6RXT32
Bundle ID: app.emotionstudio.sushtwo
Feedback: FB25577785

What we see:

  • The Sign in with Apple sheet opens. After the user confirms, the sheet shows "Sign Up Not Completed" and iOS shows "Could Not Connect – Make sure you are connected to Wi-Fi or your cellular network."
  • The app receives ASAuthorizationError 1000. AuthKit logs AKAuthenticationError -7034.
  • On one device, the akd log shows the SRP request answered with HTTP 503.
  • No request reaches our backend. The same phone reaches our backend normally at the same seconds.
  • Some testers succeed on a later attempt.

Latest occurrence: November 16, 2026, 15:57 UTC, iPhone18,2, iOS 26.6.2, Wi-Fi, TestFlight build. Also seen on iOS 27.2.1.

Configuration checked: Sign In with Apple enabled as a primary App ID, no server-to-server notification endpoint, com.apple.developer.applesignin = ["Default"] in the signed build and the App Store profile, agreements accepted, membership active.

@Paris X Pinkney, could you check our team as well?

Same issue on another team.

Team ID: XF7DFF3282
Bundle ID: ai.wildflowerlabs.DateNightDishes (live on the App Store)
Feedback ID: FB25599960

Since Nov 15, first-time Sign in with Apple sign-ups fail with "Could Not Connect" on iOS 27.0 and 27.2, on home Wi-Fi with no VPN and away from home. No request reaches our server. Returning users sign in normally. One new user on iOS 26.5 succeeded the same hour.

Paris, could you include our team in the investigation? Thank you.

We are seeing the same failure on Team NDXNQ5M4K4. Feedback: FB25427743.

The Sign in with Apple sheet appears, the user continues with Face ID, and the sheet then shows "Sign Up Not Completed". The app receives ASAuthorizationError 1001 with an empty userInfo and no identity token. It reproduces on several devices (iOS 26.5.2 and 27.0.1), in development builds and in a live App Store build.

Scope: every App ID we have registered since about 24 June 2026 fails. App IDs registered before that date still work on the same device and Apple Account, including first-time sign-ups. A newly created Services ID fails the same way on the web with invalid_client.

Minimal repro: a SwiftUI app with only a SignInWithAppleButton fails on a new App ID and works on an older one, on the same phone and Apple Account. The affected client IDs are in the Feedback.

Server response on a failing App ID (Accounts/AuthKit profile installed): ec = -24000, em = "Invalid client.", hsc = 200, ptxid = 0c6f0103-1c90-427b-87be-1364e1665ee6. On a working App ID the same phone logs "Successful SRP!".

Ruled out on our side: entitlements and provisioning profile contents (32 archives checked), a new certificate and profile, turning the capability off and on, grouping under a working primary App ID, how the App ID is created (App Store Connect API or Xcode automatic signing), and React Native.

Could the Sign in with Apple registrations for this team be checked? We have nothing left to change on our side.

We're seeing the same issue. Since about 01:00 UTC on Nov 14, 2026, the share of devices that get ASAuthorizationError 1000 on a first-time Sign in with Apple went from ~16% to ~45%. It is ~25% since Nov 17, so still not back to normal.

The error comes after the user completes Face ID or the password in the Apple sheet (median 7.3 s from tap to error, against 2.1 s before Nov 14), and our server is never called. About half of retries fail again. Most of it is on iOS 26 and 27.

Same app build before and after, all agreements are active, and the App ID configuration did not change.

Filed as FB25625337.

Same issue here since Nov 14, with no change to the app or to the App ID configuration.

The app is an iPad and iPhone app in TestFlight external testing. Sign in with Apple is its only sign-in method. The capability is enabled on a primary App ID, and new accounts were created normally on Nov 13 and Nov 14.

What testers see: the system sheet ends with "Sign Up Not Completed" (French devices: "Inscription incomplète"). Others reported "Could not connect" and "the code never came".

What the app receives: ASAuthorizationError 1001 (canceled) or 1000, and no credential.

What the server sees: nothing. On Nov 16, between 07:19 and 08:30 UTC, 10 devices launched the same TestFlight build. 5 completed Sign in with Apple and created an account. The other 5 never sent an identity token to the server (4 of them between 07:19 and 07:23 UTC). Devices were on iOS 26.5 and iOS 27.0.

Sign-ins that go through work end to end on the same build. Apple's system status pages list no incident. We have not yet compared Wi-Fi and cellular on a failing device, as suggested above.

Workaround shipped meanwhile: when the Apple sheet does not finish, the app offers "Continue without an account".

The App ID, build numbers and exact timestamps are available to an Apple engineer on request.

We are experiencing the same com.apple.AuthenticationServices.AuthorizationError Code=1000/1001 error since the 14th of Nov. I created a feedback and added some logs as well.

Feedback ticket is: FB25595302

Basically Apple authentication servers sometimes respond with a 503 and an HTML file, other with a 401 and based on that it either shows the 1000 or the 1001 error.

The only workaround so far is to keep trying, which I think makes things even worse as it creates even more traffic towards Apple own servers...