Sign in with Apple fails for new users only since Nov 14 ("connection problem"), returning users work

Since November 14, 2026 around 08:57 CET, new users can no longer create an account in our iOS app with Sign in with Apple. Users who have used Sign in with Apple with our app before still sign in normally.

What happens

  • New user taps Sign in with Apple → Apple's sheet shows "Verbindungsproblem" (connection problem).
  • The app receives ASAuthorizationError 1000 (unknown); no identity token is returned.
  • Our backend never receives a request.
  • Seen on iOS 26.3 through 27.2, multiple devices and users, all day.

What still works

  • Returning users: sign-in works.
  • An existing user who removed our app under Settings → Sign in with Apple and signed in again succeeded, but Apple reused their existing user identifier. So only creating a new identifier seems to fail.

What we checked

  • No changes to the App ID, Sign in with Apple capability, Services IDs, keys or entitlements.
  • Same app build created 8 new Sign in with Apple accounts on Nov 13.
  • Membership, agreements, tax and banking all Active.

Is anyone else seeing new-user Sign in with Apple failures since Nov 14? Apple folks: is there a known issue with creating new user identifiers?

Bundle ID: com.paulschmidt.complete

anyone else having this issue

Yes, we are seeing the same thing in our iOS app, starting a few hours earlier.

Our first failure of this kind was at 04:07 UTC on 14 November (our last normal first-time sign-up was 02:36 UTC). Since then most first-time Sign in with Apple authorisations fail with ASAuthorizationError.unknown (1000), 6 to 20 seconds after the tap, after the person has completed the sheet. Returning users sign in normally and our backend never receives a request for the failures.

For us it is not total: of the first 10 new people who got a result from the sheet, 7 never signed in and 3 did, two of them only on the 3rd and 5th attempt. We see it on iOS 26.5 to 26.7, on the current App Store build and the previous one, in several countries.

We also saw what you describe with an existing user: after Stop Using in Settings, signing in again succeeded.

No changes on our side to the App ID, capability, entitlements or the authorisation request. There is also a public status incident from another large iOS app today describing Sign in with Apple failing mainly for new accounts, opened 07:11 UTC, so this does not look specific to either of us.

We have opened a Developer Support case and I will add a Feedback Assistant number here once we have a sysdiagnose from a failing device.

Seeing the same thing on our app. Also impacting major apps like Claude: https://status.claude.com/incidents/ct4c2pwf2xpj

Pretty urgent issue impacting tons of users across so many different apps. Can someone from Apple confirm they're aware of the problem? The system status page shows that there's no issue.

Same issue on our side: Sorare Snatch (https://apps.apple.com/app/id6760656221), filed as FB25576136.

  • Only first-time Sign in with Apple fails: the sheet completes, then ASAuthorizationError.unknown (1000) after a few seconds, with no identity token. Users who signed in before are unaffected, and our backend never receives a request for the failed attempts.
  • Our first blocked users appear around 01:50 UTC on 14 November. It became constant from about 06:30 UTC.
  • About 45% of first-time sign-ins fail, against roughly 10% normally. It is worst on iOS 26.5 to 26.7 (about 70%), and also elevated on iOS 27.0 to 27.3 (about 30%).
  • It is partial: many users retry, and some get through after several attempts.
  • No app release or App ID, capability or entitlement change on our side. The same build worked normally from 9 to 13 November.

Apple folks: FB25576136 has our timestamps and numbers if that helps link the reports.

FB25574765 for us

We are also seeing similar Sign in with Apple failures since November 14, 2026.

Our observations:

  • The authorization fails with ASAuthorizationError.unknown (1000).
  • Apple’s sign-in sheet displays a connection error.
  • No identity token is returned, and the failed attempts do not reach our backend.
  • The issue occurs across multiple iOS versions.

We have not yet confirmed whether the failures are limited to first-time Sign in with Apple authorizations.

Could someone from Apple confirm whether this is a known issue and advise on any recommended workarounds? Guidance on which diagnostic logs or profiles to collect from an affected device would also be appreciated.

Same here, from 14 Nov 2026 ~00:20 UTC (earliest onset in this thread so far). Language-learning app, a few hundred Sign in with Apple attempts a day. The same builds that worked on 13 Nov started failing at that hour. We found no change in our app code or server deploys at that time.

  • The drop is in first-time sign-ups: new Sign in with Apple accounts fell from about 650 a day (10-13 Nov) to 265 on 14 Nov. Apple IDs that already authorized the app keep signing in at their usual rate.
  • Devices that completed Sign in with Apple, same app builds, before vs after the start:
    • iOS 26.5: 93% -> 34%
    • iOS 26.6: 92% -> 31%
    • iOS 27.0: 92% -> 54%
    • iOS 27.2: 90% -> 64%
  • ASAuthorizationError 1000 (unknown) arrives a median 11.6 s after the tap, about the same delay as a successful sign-in (median 12.5 s), which suggests it fails late, after the user confirms. No credential reaches the app.
  • Sticky per device: of 156 devices that failed twice, 140 never got through.
  • One data point: on an Apple ID that had used the app before (then Settings > Sign in with Apple > Stop Using), the sheet showed the create-account path, akd logged "Application has been previously authorized ... Skipping satori verification", and sign-in succeeded. We don't have a device log of a failing attempt yet.

Feedback: FB25582922. Please link it with FB25576136 and FB25574765.

Update: we captured a device log of a failing first-time sign-up (15 Nov 2026 13:19 UTC, iOS 26.6.2, an Apple ID that had never used the app, failing twice in a row):

  • After Face ID, akd logs "No password, but CK is available. Will ask for ck-based auth", then "Performing SRP request".
  • The server answers HTTP 503 with a 190-byte body that doesn't parse (AppleIDAuthSupport Code=6, "Failed to get response from server").
  • akd: "Network error. Retrying auth once..." and gets 503 again.
  • Then AKAuthenticationError -7005 (the "connection" alert the user sees, on a working network) and -7034 to the app, which surfaces as ASAuthorizationError 1000.

No "satori" line is reached. So the account authentication step (SRP) itself returns 503 for these Apple IDs, before anything app-specific. Added to FB25582922.

More info for Apple Engineers:

Users try to sign in and see "Sign Up Not Completed". Then an error message pops up that says "Could Not Connect" "Make sure you are connected to Wi-Fi or your cellular network."

We’re seeing a clear spike in Sign in with Apple errors (AuthorizationError code 1000) in our graphs. Anthropic is also reporting a Sign in with Apple incident (https://status.claude.com/incidents/ct4c2pwf2xpj), which may be related. I filed this with Apple: FB25587150 (https://feedbackassistant.apple.com/feedback/25587150).

FB25591173 for us. 48 hours and counting. Has anyone heard from Apple?

The issue still hasn't been resolved. November 14 was the day of my app's promotional campaign, and because of this outage, I missed out on a wave of potential new users and received two negative reviews on the App Store. Yet Apple's System Status page continues to show that all services are operating normally.

This is also an issue for us. I am a bit surprised that no response or aknowledgement from Apple is taking place

Same issue on our side (Wikicards, iOS), filed as FB25575615.

Only the Sign in with Apple sheet is affected: it completes, then ASAuthorizationError.unknown (1000) comes back after 3 to 60 seconds, with no identity token, and our backend never gets a request. Our failure rate per attempt jumped at about 00:30 UTC on 14 November, from 4 to 10% to around 66%. The same build that shipped with no OTA update went from 3.9% to 66.6% failures overnight, so it is not a change on our side.

It depends clearly on the iOS major version. Since 14 November, per attempt: iOS 18 at 10% (about 6% before), iOS 26 at 85% (9% before), iOS 27 at 68% (10% before). iOS 16 and 17 look normal, but our sample there is small.

Per person it is less severe, because retries do get through for us. On iOS 26, about a third of the people who tried never succeeded. On iOS 27.0 and 27.2 it is 13 to 16%. On 27.3 it is 2 out of 24 so far, which is too few to conclude. On iOS 18, 2 out of 167.

No change to our App ID, capability, keys or entitlements. Apple folks, FB25575615 is ours if it helps link the reports.

In my case:

New user
Taps Sign in with Apple -> Share My Email -> Works
Taps Sign in with Apple -> Hide My Email -> Connection Problem

This is affecting all of our apps, and has made our sign-in rate absolutely plummet.

This issue is high severity and going on for several days now. Can we please have an Apple engineer's eyes on this?

I've filed https://feedbackassistant.apple.com/feedback/25600814

This is the same for us and sign in with apple is our most chosen sign in method.

seems to be resolved, anthropic marked it as resolved and its good on our side too