Sign in with Apple Failure, AKAuthenticationServerError=-24000

Privacy & Security Sign in with Apple
CHENJIACHENG OP
Created 4d
Replies 0
Boosts 0
Views 43
Participants 1

Apple Developer Support Request - Sign in with Apple Failure

Date prepared: 2026-07-08 App name: LingJing / XiaoLing Bundle ID: com.jachymchen.xiaoling Apple Developer Team ID: 765B64SW9Z Platform: iOS

Summary

Sign in with Apple fails before the app receives a usable Apple identity token. The user-facing Apple system sheet ends with the Chinese alert "未完成注册" ("Sign Up Not Completed"). The app callback does not receive an identityToken, so our backend auth provider is not reached successfully.

We reproduced the same failure in a minimal native Swift app that only uses AuthenticationServices and the same Bundle ID / provisioning profile, without Supabase or any app-specific backend code. This suggests the failure is likely in the Apple Sign in with Apple authorization flow, account/device state, or App ID/provisioning configuration recognized by Apple's auth services, rather than in our app's backend implementation.

Environment

Mac:

  • macOS 26.5
  • Apple Silicon MacBook Pro
  • Xcode 26.5

iPhone:

  • Real device connected over USB
  • Device name: 硬糖的iPhone
  • iOS 26.5.1
  • Device UDID: 00008150-000344540C99401C

App:

  • Bundle ID: com.jachymchen.xiaoling
  • App version currently used for testing: 0.1.0
  • App Store Connect app ID observed during TestFlight work: 6784075688
  • TestFlight build upload previously succeeded for version 0.1.0 build 2

Provisioning / Entitlements Checked

Development provisioning profile:

  • Profile name: XiaoLing Dev
  • application-identifier: 765B64SW9Z.com.jachymchen.xiaoling
  • com.apple.developer.applesignin: [Default]
  • com.apple.developer.team-identifier: 765B64SW9Z
  • get-task-allow: true
  • keychain-access-groups includes:
    • 765B64SW9Z.*
    • com.apple.token
  • Profile includes the test device UDID:
    • 00008150-000344540C99401C
  • Expiration: 2027-06-27

Distribution / TestFlight provisioning profile:

  • Profile name: XiaoLing AppStore
  • application-identifier: 765B64SW9Z.com.jachymchen.xiaoling
  • com.apple.developer.applesignin: [Default]
  • beta-reports-active: true
  • get-task-allow: false

Signed app entitlements were checked from the executable and matched the expected Bundle ID / Team ID / Sign in with Apple entitlement.

Important note:

  • Running codesign -d --entitlements :- XiaoLing.app against the .app bundle may print an "invalid entitlements blob" style result.
  • Running codesign against the actual executable inside the .app is the useful check, and that showed the expected entitlements.

Reproduction Steps

  1. Install and launch the iOS app with Bundle ID com.jachymchen.xiaoling on the real iPhone.
  2. Tap "Sign in with Apple".
  3. Complete the Apple ID system prompt.
  4. The Apple system flow fails and shows "未完成注册".
  5. The app does not receive a valid ASAuthorizationAppleIDCredential identity token.

Observed Result

The Apple authorization flow fails before returning a usable credential to the app. The system UI shows "未完成注册" ("Sign Up Not Completed").

Expected Result

AuthenticationServices should return an ASAuthorizationAppleIDCredential with an identityToken so the app can continue its own backend sign-in.

Key Device Logs Observed

During real-device attempts, the following log lines appeared around the failure:

  • AuthKit continuation-key-creation token is missing
  • AppleIDAuthSupport: setError: 2:M2 missing (bad password)
  • SRP authentication with server failed
  • AUTH_ALERT_SIGN_UP_NOT_COMPLETED -> 未完成注册
  • AKRemoteViewController did complete with authorization (null)
  • AKAuthenticationServerError Code=-24000

The private framework error code by itself is not enough to identify the root cause, but the flow consistently fails inside Apple's AuthKit / Apple ID authorization path before our app receives an identity token.

Minimal Native Demo Test

To exclude app-specific implementation and backend issues, we created a minimal native SwiftUI app using only:

  • AuthenticationServices
  • SignInWithAppleButton
  • ASAuthorizationAppleIDProvider
  • The same Bundle ID: com.jachymchen.xiaoling
  • The same Team ID / provisioning entitlement setup
  • No Supabase
  • No custom backend
  • No React Native
  • No third-party auth library

The minimal native demo produced the same user-facing failure: "未完成注册".

This strongly suggests the issue is not caused by Supabase, nonce hashing, OAuth handling, React Native, or our app UI. The failure happens before any backend auth exchange can occur.

Additional Context

  • The tester tried another Apple ID and still reproduced the failure.
  • The tester stated the Apple ID itself is otherwise usable.
  • The app's Bundle ID is intended to be exactly:
    • com.jachymchen.xiaoling
  • We specifically checked for provisioning profile / Bundle ID mismatch and did not find a mismatch in the installed build.

Questions for Apple Developer Support

  1. Can Apple check whether App ID 765B64SW9Z.com.jachymchen.xiaoling has any server-side Sign in with Apple configuration issue?
  2. Can Apple explain what conditions produce:
    • AUTH_ALERT_SIGN_UP_NOT_COMPLETED
    • AKAuthenticationServerError Code=-24000
    • "M2 missing (bad password)"
    • "AuthKit continuation-key-creation token is missing"
    in a native AuthenticationServices Sign in with Apple flow?
  3. Is there any known issue on iOS 26.5.1 or with development-signed apps where Sign in with Apple fails before returning an ASAuthorizationAppleIDCredential?
  4. Are there account-level or device-level requirements beyond normal Apple ID login that can cause Sign in with Apple to show "Sign Up Not Completed"?
  5. Can Apple verify whether this Bundle ID / Team ID is correctly enabled for Sign in with Apple on Apple's backend?

Minimal Code Shape Used for Native Demo

The native demo used a standard SignInWithAppleButton:

SignInWithAppleButton(.signIn) { request in
    request.requestedScopes = [.fullName, .email]
} onCompletion: { result in
    switch result {
    case .success(let authorization):
        // Check authorization.credential as ASAuthorizationAppleIDCredential
        // and read identityToken.
    case .failure(let error):
        // Log NSError domain, code, localizedDescription, and userInfo.
    }
}

Support Request

Please help determine why Apple's Sign in with Apple authorization flow fails for Bundle ID com.jachymchen.xiaoling before returning a credential, despite the app having the Sign in with Apple entitlement and matching provisioning profile / Bundle ID.

Replies  0
Boosts  0
Views  43
Participants  1
Sign in with Apple Failure, AKAuthenticationServerError=-24000
First post date Last post date
 
 
Q