Sign in with Apple fails after Face ID in both our app and Apple's Juice sample

Question

Created 2d

Replies 1

Boosts 0

Participants 1

I am looking for help diagnosing a Sign in with Apple failure that occurs after Face ID and before a credential is returned.

Environment

iPhone 15 Pro
iOS 26.2
Xcode 26.3
TestFlight distribution builds
Team ID 42U……D944
Bundle IDs
- com.vybers.vybers-ios
- com.vybers.vybers

Reproduction

Install the app from TestFlight.
Tap Sign in with Apple.
Complete Face ID.
Face ID succeeds but the authorization sheet reports that registration could not be completed.
The app receives no ASAuthorizationAppleIDCredential and no identityToken.

The same behavior occurs

Across multiple builds.
On multiple physical devices.
With multiple Apple IDs.
In both Bundle IDs belonging to the same team.
In Apple's official Juice sample app using the official Sign in with Apple flow.

Control experiment The same iPhone successfully signs in with Apple in a newly downloaded unrelated App Store app.

The relevant device log captured immediately after the failure includes

Apple server response HTTP 200 AppleIDAuthSupport setError 2M2 missing bad password SRP authentication with server failed AKRemoteViewController did complete with authorization null AKAuthenticationServerError Code=-24000

The “bad password” text is confusing but the Apple ID works in unrelated apps and the failure happens after successful Face ID. The application server is never contacted because no credential or identityToken is produced.

Could this be caused by a team-scoped Sign in with Apple/AuthKit registration or synchronization problem rather than by the client implementation or server-side token verification

In particular I would appreciate guidance on

Checking the Sign in with Apple registration for the team.
Checking whether multiple client IDs in one team can become stale or out of sync.
Whether an individual Developer Program membership changes any requirement for this flow.
Which diagnostic information Apple needs to investigate the AuthKit backend response.

I can provide the full Team ID build details signing entitlements and a sysdiagnose through a private support case.

Answer 1

wzbbiao OP

1d

Update (July 31, 2026): We ran a clean cross-team control experiment with Apple's unmodified official Juice sample.

On the same physical iPhone 12 Pro (iOS 26.3.1), with the same Apple ID and Face ID:

Team FNDQRVAXU4, App ID com.vybers.placeholder.vybersworld.fndqrvaxu4, signed with an Apple Development profile containing com.apple.developer.applesignin = Default: Sign in with Apple succeeded and Juice received ASAuthorizationAppleIDCredential.
Team 42U93YD944: our app and an official Juice build signed for that team both failed after Face ID. The sheet said registration could not be completed; no credential or identityToken was returned. The device log included AKAuthenticationServerError Code=-24000.

The successful app was installed directly on the same phone. Its signed entitlements were verified for the matching application-identifier/team-identifier and com.apple.developer.applesignin = Default.

This isolates the problem to a likely team-scoped Sign in with Apple/AuthKit backend registration or synchronization issue in 42U93YD944, rather than the Apple ID, device, Face ID, client code, signing capability, or token verification. Please compare the backend state for 42U93YD944 and FNDQRVAXU4 and resynchronize if needed. Logs and signing details are available under support case 20000123689964.