Post

Replies

Boosts

Views

Activity

Reply to Sign in with Apple: "Sign Up Not Completed" for every App ID in our team — framework returns canceled (1001) with empty userInfo
Same issue here. Team ID: GJP7Y5Q68D Sign in with Apple fails for every App ID in our team. The system sheet appears, the user picks an account, and authorization then fails with an empty ASAuthorizationError (1000/1001). No request ever reaches our backend. akd logs match this thread exactly: Encountered error while fetching developer team: Error Domain=AKSQLError Code=-6003 AuthKit continuation-key-creation token is missing! No password, but CK is available. Will ask for ck-based auth. Failed to fetch device token. Proceeding with cert headers. Error: AKAuthenticationError Code=-7027 AppleIDAuthSupport: setError: 2:M2 missing (bad password) SRP authentication with server failed! Error Domain=com.apple.AppleIDAuthSupport Code=2 Both HTTPS requests to the Apple ID server return status 200, so this is not a networking problem. Ruled out on our side: Minimal test case: a brand-new App ID (com.rm.siwaprobe, created 2026-09-01) with Sign in with Apple enabled as a primary App ID, and a single-screen SwiftUI app containing nothing but one SignInWithAppleButton. Fails identically. Entitlement verified in the signed binary (codesign -d --entitlements) and in the decoded embedded.mobileprovision: com.apple.developer.applesignin = ["Default"] Capability removed and re-added via App Store Connect API — no change. Profiles regenerated, clean build, fresh install on physical devices. Two different iPhones with two different personal Apple IDs. Same Apple ID signs in successfully with apps from other teams on the same device. iCloud and Media & Purchases set to the same Apple ID — no change. Screen Time restrictions off, personal (not managed) accounts. All agreements accepted, membership active. Impact: our production app (com.rm.fitnessassistant) has zero successful Sign in with Apple registrations since launch, and App Review rejected our build under Guideline 2.1(a) on 2026-08-12 for exactly this failure — the reviewer hit the same wall. Feedback: FB<номер> Could a server-side fix be applied to team GJP7Y5Q68D as was done for other teams in this thread?
Topic: Privacy & Security SubTopic: Sign in with Apple Tags:
8h
Reply to Sign in with Apple: "Sign Up Not Completed" for every App ID in our team — framework returns canceled (1001) with empty userInfo
Same issue here. Team ID: GJP7Y5Q68D Sign in with Apple fails for every App ID in our team. The system sheet appears, the user picks an account, and authorization then fails with an empty ASAuthorizationError (1000/1001). No request ever reaches our backend. akd logs match this thread exactly: Encountered error while fetching developer team: Error Domain=AKSQLError Code=-6003 AuthKit continuation-key-creation token is missing! No password, but CK is available. Will ask for ck-based auth. Failed to fetch device token. Proceeding with cert headers. Error: AKAuthenticationError Code=-7027 AppleIDAuthSupport: setError: 2:M2 missing (bad password) SRP authentication with server failed! Error Domain=com.apple.AppleIDAuthSupport Code=2 Both HTTPS requests to the Apple ID server return status 200, so this is not a networking problem. Ruled out on our side: Minimal test case: a brand-new App ID (com.rm.siwaprobe, created 2026-09-01) with Sign in with Apple enabled as a primary App ID, and a single-screen SwiftUI app containing nothing but one SignInWithAppleButton. Fails identically. Entitlement verified in the signed binary (codesign -d --entitlements) and in the decoded embedded.mobileprovision: com.apple.developer.applesignin = ["Default"] Capability removed and re-added via App Store Connect API — no change. Profiles regenerated, clean build, fresh install on physical devices. Two different iPhones with two different personal Apple IDs. Same Apple ID signs in successfully with apps from other teams on the same device. iCloud and Media & Purchases set to the same Apple ID — no change. Screen Time restrictions off, personal (not managed) accounts. All agreements accepted, membership active. Impact: our production app (com.rm.fitnessassistant) has zero successful Sign in with Apple registrations since launch, and App Review rejected our build under Guideline 2.1(a) on 2026-08-12 for exactly this failure — the reviewer hit the same wall. Feedback: FB<номер> Could a server-side fix be applied to team GJP7Y5Q68D as was done for other teams in this thread?
Topic: Privacy & Security SubTopic: Sign in with Apple Tags:
Replies
Boosts
Views
Activity
8h