Same confirmed server-side registration failure for Chrona, Inc.
Team ID: ZC697J3VQ4
Affected primary App IDs:
Gentium: A94TXV6J23 / com.gentiumcapital.contractor
Cluby: J49QQZ5CQW / com.chrona.cluby
Both App IDs have APPLE_ID_AUTH with PRIMARY_APP_CONSENT, and the signed apps and provisioning profiles contain com.apple.developer.applesignin = [Default]. On-device akd logs show AKSQLError -6003, “No applications were found with the provided Client ID,” followed by AKAuthenticationServerError -24000. Apple’s public authorization endpoint independently returns invalid_client / -24000 for both clients, while older Sign in with Apple clients in the same team are recognized. No credential is returned and no request reaches our backend.
Feedback Assistant: FB24630675 (submitted under the Chrona, Inc. team with the evidence attached).
@Paris X Pinkney — could Apple please apply the same server-side registration repair/re-provisioning used for the other resolved teams in this thread to these two App IDs? We can provide additional diagnostics if engineering requests them.
Topic:
Privacy & Security
SubTopic:
Sign in with Apple
Tags: