Update with Accounts/AuthKit sysdiagnose evidence from TestFlight 1.0.0 (5): LAYR now has the exact failure signature reported by other affected teams.
On 2026-08-22 at 01:49:49 and 01:57:20 +0800, akd derived the correct identifiers from the signed app:
clientID: cc.brue.layr
teamID: 5RCJW4N328
It then logged:
Fetching developer team for client with ID: cc.brue.layr
AKSQLError Code=-6003
No applications were found with the provided Client ID: cc.brue.layr
The Apple network request itself completed successfully with HTTP 200, but Apple’s AuthKit response was:
ec = -24000
em = Invalid client.
ptxid ab797933-b4db-443c-ba9e-9667d10db920
ptxid 43bf2953-2933-4cef-b3ff-3131131f8bc2
For the second capture, biometric authentication completed successfully immediately before this response. AuthKit then returned authorization (null); no Apple credential or identity token reached LAYR.
We also removed and re-added the Sign in with Apple capability, deleted the old distribution profile, generated a fresh App Store profile, rebuilt, and uploaded build 5. The signed binary still contains application-identifier = 5RCJW4N328.cc.brue.layr and com.apple.developer.applesignin = [Default]. The fresh build fails identically.
This rules out the app backend, JWT/client-secret generation, and stale provisioning as the failure point. @Paris X Pinkney, could Apple please repair/re-provision the server-side Sign in with Apple registration lookup for Team 5RCJW4N328, App ID 3F7B7MNFHY, bundle cc.brue.layr? A fresh sysdiagnose is available.
Topic:
Privacy & Security
SubTopic:
Sign in with Apple
Tags: