Sign in with Apple fails with "Sign-Up not completed" (ASAuthorizationError 1001) for all apps of our team, on all devices — other teams' apps work fine

Question

Created 6d

Replies 2

Boosts 1

Participants 3

Sign in with Apple fails with the system alert "Sign-Up not completed" for every app belonging to our developer team, on every device we tested. The app itself only receives ASAuthorizationError code 1001 with an empty userInfo dictionary, so there is nothing actionable on the client side.

We have systematically ruled out every configuration cause we could think of:

Sign in with Apple capability is enabled on each App ID, set as primary (verified via the App Store Connect API)
com.apple.developer.applesignin entitlement is present in the signed binaries and in the provisioning profiles (verified with codesign and security cms)
Two-factor authentication is active on the test Apple ID
No pending agreements (Paid Apps accepted; one of our apps is live on the App Store)

Reproduction matrix — ALL of these combinations fail identically:

Devices: two different physical devices (iPhone, iPad)
Signing: development-signed AND TestFlight (App Store distribution) builds
Network: Wi-Fi AND cellular
App IDs: existing ones (capability enabled more than 48 hours ago) AND a minimal reproduction app whose App ID + capability were created minutes before the test

Control test that WORKS: on the same devices, with the same Apple ID, a brand-new Sign in with Apple sign-up in App Store apps from other teams completes without any issue. The failure is therefore strictly scoped to apps of our team.

The device log (log collect) shows the following akd sequence at the moment of every attempt:

akd: [com.apple.authkit:siwa] Encountered error while fetching developer team: Error Domain=AKSQLError Code=-6003 akd: [com.apple.aaafoundation:log] Error fetching keychain items - NSOSStatusErrorDomain Code=-25300 "no matching items found" akd: [com.apple.authkit:siwa] Using personal credential state - 2, error - AKAuthenticationError Code=-7074 akd: [com.apple.AppleIDAuthSupport:general] AppleIDAuthSupport: setError: 2:M2 missing (bad password) akd: [com.apple.authkit:core] SRP authentication with server failed! (com.apple.AppleIDAuthSupport Code=2) akd: [com.apple.authkit:siwa] Error performing auth request: AKAuthenticationError Code=-7003

Given that a freshly created App ID reproduces the failure immediately while other teams' apps work on the same devices with the same Apple ID, this looks like a broken server-side Sign in with Apple provisioning/registration state for our team rather than anything we can fix ourselves.

Has anyone seen this resolved? Is there anything on the account/team level that can get a team's Sign in with Apple provisioning re-initialized? Happy to share the Team ID and full .logarchive with Apple folks via DTS/support.

Answer 1

LourdeJones OP

3d

Seeing the identical failure on our team (Team 5FSJ73AXHD), app com.stillstandingstudios.examineTheScriptures — same AKAuthenticationError -7003 / ASAuthorizationError 1001 ("Sign Up Not Completed"), thrown right after Face ID succeeds.

We've verified the same things you have: Sign in with Apple enabled on the App ID as primary with an empty Server-to-Server endpoint; com.apple.developer.applesignin present in the entitlements and granted in the embedded provisioning profile (confirmed on both debug and TestFlight release builds); 2FA on; no pending agreements. Google and email/password sign-in work fine in the same build, and it fails identically on debug and TestFlight.

Adding a +1, and happy to share our Team ID and a .logarchive with Apple via DTS.

Has anyone from DTS been able to look at a team's Sign in with Apple provisioning state? This looks entirely server-side.

Answer 2

shely OP

2d

Same exact failure signature here, on Team U3KSLBV22Q, Bundle ID com.yyssd.

Feedback ID: FB23839261

Captured sysdiagnose with AuthKit profile installed, the akd failure chain is identical to the original report:

akd: [authkit:siwa] Encountered error while fetching developer team: Error Domain=AKSQLError Code=-6003 akd: [authkit:siwa] No applications were found with the provided Client ID: <private> akd: [authkit:siwa] Using personal credential state - 2, error - AKAuthenticationError Code=-7074 akd: [authkit:core] Performing SRP request with context akd: [AppleIDAuthSupport] setError: 2:M2 missing (bad password) akd: [authkit:core] SRP authentication with server failed! akd: [authkit:siwa] Error performing auth request: AKAuthenticationError Code=-7003 What we've exhaustively verified (all PASS):

SIWA capability enabled on App ID via App Store Connect API (APPLE_ID_AUTH + PRIMARY_APP_CONSENT) Tried deleting and recreating the capability via API — same failure com.apple.developer.applesignin present in entitlements and embedded provisioning profile (verified via security cms -D) iOS 26.5.2 (23F84) — production, not beta Tried two different Apple IDs — both fail identically Tried deleting app + "Reset Location & Privacy" — same failure No prefix conflict (removed SIWA from sibling App ID com.yyssd.game) — same failure App Store Connect API shows the App ID is registered correctly Control test that WORKS: on the same iPhone 13, with the same Apple ID, at the same time, SIWA in App Store apps from other teams (Notion etc.) completes without issue.

The failure is therefore strictly scoped to Team U3KSLBV22Q. The AKSQLError -6003 "No applications were found with the provided Client ID" line from akd is the smoking gun — Apple's backend does not recognize com.yyssd as having SIWA enabled, despite the App Store Connect API showing otherwise.

Happy to share the full sysdiagnose logarchive via DTS. Please advise on next steps to get the team's SIWA provisioning re-initialized server-side.