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 failure signature, another affected team — adding a data point and requesting the same server-side team-registration fix. Team ID: NY3P8QZG56 Bundle ID: kr.canalwalk.app (App Store app ID 6800445181), App ID registered 2026-08-16, Sign in with Apple enabled the same day. Still in Prepare for Submission. Device: iPhone 15 (iPhone15,4), iOS 17.4.1 (21E619), TestFlight build 0.3.0 (18). Feedback Assistant: FB24373549 (sysdiagnose + Accounts/AuthKit log archives attached). Symptom: The native Sign in with Apple sheet renders, Face ID completes, then the sheet fails; no credential is returned to the app. No authorization request ever reaches our backend. akd shows the same backend team-lookup failure reported throughout this thread: akd [authkit:siwa] Setting clientID to <kr.canalwalk.app> akd [authkit:siwa] Setting teamID to akd [authkit:siwa] Fetching developer team for client with ID: <kr.canalwalk.app> 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: <kr.canalwalk.app> A few seconds later the SRP submit fails with "M2 missing (bad password)" -> AKAuthenticationServerError -24000, i.e. the "bad password" is a symptom of the -6003 team lookup, not an actual password problem. Reproduced across three separate log captures on 2026-08-17. Client configuration verified (not just in the portal): App Store Connect API reports APPLE_ID_AUTH with APPLE_ID_AUTH_APP_CONSENT = PRIMARY_APP_CONSENT for kr.canalwalk.app. The team contains no wildcard App IDs; every App ID in the team is explicit. The signed binary carries application-identifier = NY3P8QZG56.kr.canalwalk.app and com.apple.developer.applesignin. Toggling the capability off/on (2026-08-17) changed nothing. Program agreements are active. Control: On the same device and Apple Account, an app from this team that was authorized earlier continues to sign in normally via Sign in with Apple — so the device/account SIWA stack itself is functional; only the first-time sign-up for the newly registered App ID hits -6003. This is the exact signature Apple resolved server-side for other teams in this thread (e.g. GW7XA5CX69, self-resolved 2026-07-31 with no client changes). Could someone from Apple please check the server-side Sign in with Apple team registration for NY3P8QZG56 / kr.canalwalk.app? Thank you.
2w
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 failure signature, another affected team — adding a data point and requesting the same server-side team-registration fix. Team ID: NY3P8QZG56 Bundle ID: kr.canalwalk.app (App Store app ID 6800445181), App ID registered 2026-08-16, Sign in with Apple enabled the same day. Still in Prepare for Submission. Device: iPhone 15 (iPhone15,4), iOS 17.4.1 (21E619), TestFlight build 0.3.0 (18). Feedback Assistant: FB24373549 (sysdiagnose + Accounts/AuthKit log archives attached). Symptom: The native Sign in with Apple sheet renders, Face ID completes, then the sheet fails; no credential is returned to the app. No authorization request ever reaches our backend. akd shows the same backend team-lookup failure reported throughout this thread: akd [authkit:siwa] Setting clientID to <kr.canalwalk.app> akd [authkit:siwa] Setting teamID to akd [authkit:siwa] Fetching developer team for client with ID: <kr.canalwalk.app> 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: <kr.canalwalk.app> A few seconds later the SRP submit fails with "M2 missing (bad password)" -> AKAuthenticationServerError -24000, i.e. the "bad password" is a symptom of the -6003 team lookup, not an actual password problem. Reproduced across three separate log captures on 2026-08-17. Client configuration verified (not just in the portal): App Store Connect API reports APPLE_ID_AUTH with APPLE_ID_AUTH_APP_CONSENT = PRIMARY_APP_CONSENT for kr.canalwalk.app. The team contains no wildcard App IDs; every App ID in the team is explicit. The signed binary carries application-identifier = NY3P8QZG56.kr.canalwalk.app and com.apple.developer.applesignin. Toggling the capability off/on (2026-08-17) changed nothing. Program agreements are active. Control: On the same device and Apple Account, an app from this team that was authorized earlier continues to sign in normally via Sign in with Apple — so the device/account SIWA stack itself is functional; only the first-time sign-up for the newly registered App ID hits -6003. This is the exact signature Apple resolved server-side for other teams in this thread (e.g. GW7XA5CX69, self-resolved 2026-07-31 with no client changes). Could someone from Apple please check the server-side Sign in with Apple team registration for NY3P8QZG56 / kr.canalwalk.app? Thank you.
Replies
Boosts
Views
Activity
2w