Our iOS app has used Sign in with Apple (SwiftUI SignInWithAppleButton, scopes .fullName and .email, hashed nonce) for over a year without problems. Since about 04:00 UTC on 14 November 2026, most people authorising the app for the first time fail: they tap the button, the system sheet appears, they complete it (Face ID or passcode), and 6 to 20 seconds after the tap the completion handler receives ASAuthorizationError.unknown (1000).
People who have authorised the app before sign in normally. No request reaches our server in the failing case.
What we see
Before the onset this failure was rare: about one person a week against 15 to 24 first-time sign-ups a day. In the first 12 hours after the onset, 10 people got a result from the sheet. 7 never signed in. 3 did, two of them only on the 3rd and 5th attempt.
It affects the current App Store build and the previous one, iOS 26.5 to 26.7, several iPhone models, in Canada, the US, Saudi Arabia, Qatar and Morocco, on Wi-Fi and cellular.
This is separate from the immediate 1000 a device with no Apple Account returns. Those arrive within 3 seconds and we excluded them.
What we checked
Sign In with Apple is enabled on the App ID as a primary App ID. The com.apple.developer.applesignin entitlement is unchanged. Distribution certificates are valid and the membership is active. Nothing in the authorisation request, the button or the completion handler changed between the two builds. We could not reproduce it on our own device after revoking our grant in Settings (Stop Using) and signing in again.
One possibly related fact: an updated Apple Developer Program License Agreement was issued on 29 October 2026 and we only accepted it on 14 November, about 12 hours after the failures began. We do not yet know whether the failures stopped after acceptance.
Questions
Can an unaccepted Program License Agreement degrade Sign in with Apple for first-time users, for example after a grace period?
Has anyone else seen first-time authorisations start failing around 14 November 2026 with no change on their side?
What should we capture from an affected device to identify the cause, given that we cannot reproduce it ourselves? We have no sysdiagnose from a failing attempt yet.
The code-level support form requires a sample project, and this cannot be reproduced in one, so I am asking here. I can share the team ID, bundle ID and UTC timestamps of individual failed attempts privately with an Apple engineer.
Update: this looks like the same thing as https://developer.apple.com/forums/thread/857623 (new users only since 14 November, returning users fine, agreements all active there). Our first failure was at 04:07 UTC on 14 November.