Adding a team to the list, and a controlled comparison from a single capture.
Team ID XJ5D4FX66P, bundle ID gg.wishtrap.game. Same fault as this thread:
Apple's own sheet opens, names the app correctly, Face ID succeeds, and then Apple shows
Sign-Up Not Completed. No authorization ever reaches our server.
The comparison
One idevicesyslog capture on 2026-08-31 held two Sign in with Apple sign ups 33 seconds
apart, on the same iPhone 16 Pro (iOS 26.6.1) and the same personal Apple Account. The
first was Temu (com.einnovation.temu), an App Store app from another team, and the second
was ours. Both were genuine first-time sign ups for that account.
com.einnovation.temu, 11:01:18
gg.wishtrap.game, 11:01:51
Attempting to authorize request
yes
yes
No applications were found with the provided Client ID
yes
yes
Encountered error while fetching developer team: AKSQLError Code=-6003
yes
yes
Application has no shared credentials
yes
yes
Checking for genesis event!
yes
yes
SRP stateClientNeg1 / Neg2 / Neg3
all three
all three
final SRP response body
4373 bytes, contents: <private>
733 bytes, contents: (null), M2 missing
outcome
did complete with authorization <private> (error: (null))
AKAuthenticationError Code=-7003
The pre-flight is identical line for line, the same daemon ran the same protocol, the
account had just proved it can complete a sign up, and the only variable left is which App
ID the sign up is for.
One correction to the thread's diagnosis
AKSQLError Code=-6003 and No applications were found with the provided Client ID are
not the signature of this fault. Both appear in the attempt that succeeded, 33 seconds
earlier, in the same capture. They are local cache misses during pre-flight.
Invalid value for key authType: (null) is benign for the same reason, logged on the
successful sign up as well. Of the four missing-key complaints, only acname, ut and
primary email vetted belong to the failure. The discriminator is the SRP result and
nothing before it:
akd(AppleIDAuthSupport) stateClientNeg3: <private>
akd(AppleIDAuthSupport) AppleIDAuthSupport: setError: 2:M2 missing (bad password)
akd Creating AKAuthenticationServerResponse with status: <private> contents: (null)
akd <Error> Invalid/missing value for key acname: (null)
akd ThirdPartyDeviceDataResponseHandler fromResponse serverProvidedData is nil
akd <Error> SRP authentication with server failed! Error Domain=com.apple.AppleIDAuthSupport Code=2
akd <Error> Error performing auth request: Error Domain=AKAuthenticationError Code=-7003
Runner(AuthKit) <Error> Authorization failed: Error Domain=AKAuthenticationError Code=-7003
(bad password) is the daemon's generic label for a response that carried no server proof.
It is not a statement about any password: the same stored credential completed Temu's
exchange 29 seconds earlier.
Worth noting for anyone matching symptoms: the error does reach the app here, as
AKAuthenticationError Code=-7003. Reports in this thread of canceled (1001) with an
empty userInfo are what the AuthenticationServices layer surfaces on top of it, so an
implementation that treats a cancellation as "the user closed the sheet" will hide this
fault completely.
Client side, verified rather than assumed
APPLE_ID_AUTH with APPLE_ID_AUTH_APP_CONSENT: PRIMARY_APP_CONSENT, read from the App
Store Connect API on 2026-08-31, not from the portal UI
com.apple.developer.applesignin = [Default] in the signed binary via
codesign -d --entitlements, and in embedded.mobileprovision via security cms -D
explicit primary App ID, no wildcard, no grouping, seedId XJ5D4FX66P on both
requested scopes empty and also tried with email and fullName, no difference
SHA-256 nonce, personal Apple Account with 2FA, developer mode on
reproduced on two Apple Accounts and two devices
the same account signs in successfully to other teams' apps on the same device
Google Sign-In through the same code path works end to end
The Apple Developer Program License Agreement was also accepted on 2026-08-30 after finding
it pending, which changed nothing.
Request: server side re-provisioning of the Sign in with Apple registration for team
XJ5D4FX66P. Happy to supply the filtered akd window covering both attempts, or a
sysdiagnose taken with the Accounts/AuthKit logging profile, whichever is more useful.
Topic:
Privacy & Security
SubTopic:
Sign in with Apple
Tags: