Update: captured a live device log during reproduction (Console.app, connected via cable), which confirms this exactly rather than just matching the pattern:
error akd Encountered error while fetching developer team: Error Domain=AKSQLError Code=-6003
default akd No applications were found with the provided Client ID:
default akd Client has default access level in SiwA entitlement
...
(same AKSQLError -6003 / "No applications were found" repeats a second time later in the same auth attempt)
...
error akd Error performing auth request: Error Domain=AKAuthenticationError Code=-7003
error Crossfit Tracker Authorization failed: Error Domain=AKAuthenticationError Code=-7003 UserInfo={AKClientBundleID=}
Client has default access level in SiwA entitlement confirms the entitlement itself is being read correctly by the OS — so this is specifically the team/App ID lookup failing (AKSQLError -6003, "no applications found"), not anything in our provisioning or entitlements. AKAuthenticationError -7003 is the real underlying failure; ASAuthorizationController collapses it into the generic .canceled (1001) with empty userInfo by the time it reaches the app, which is why it initially looked like a plain cancellation.
I can also reproduce the identical failure — same AKSQLError -6003 signature in Console — in a second, unrelated app under the same team: com.nulltwenty.Remoti (App Store Connect app 1567902235, "AnywhereRoles Remote Jobs"). Both apps share Team ID 2357A78TMR. This confirms the registration failure is at the team level in Apple's backend, not specific to a single App ID, matching exactly how the resolution was applied in the threads I linked above (fixed per Team ID, not per app).
This is the same AKSQLError -6003 signature described as resolved by a server-side team registration fix in those threads. Happy to provide a full sysdiagnose if that helps move this along.
Topic:
Privacy & Security
SubTopic:
Sign in with Apple