Same signature here. Feedback filed: FB25131402, with sysdiagnose (Accounts/AuthKit profile installed). Team ID: F2XZ7YY2X7 Failing bundle ID: app.blacksands.southislandguide (App ID registered late September 2026, App Store Connect app 6818057796, never completed a sign-up) Working bundle ID in the same team: app.blacksands.rtrguide (older). On the same device and Apple Account it completes a brand-new sign-up, tested today after removing its entry from Settings > Sign in with Apple. akd log, 2026-10-10 02:27 UTC, iPhone XR, iOS 18.7.10: Fetching developer team for client with ID: app.blacksands.southislandguide Encountered error while fetching developer team: AKSQLError Code=-6003 No applications were found with the provided Client ID: app.blacksands.southislandguide AppleIDAuthSupport: setError: 2:M2 missing (bad password) SRP authentication with server failed! Status={ ec = "-24009"; em = "Invalid client."; hsc = 200; ptxid = "79620fe7-a467-4148-8ce0-90a7765ec67c"; } Verified on our side: applesignin entitlement in the signed binary and the embedded profile, profile status Active, app not listed under Settings > Sign in with Apple. The public authorize endpoint returns invalid_client for the failing bundle ID and invalid_request for the working one. One difference from most reports here: the failing App ID is currently grouped under the working primary App ID (since 2026-09-30). It failed the same way before that, while it was a primary App ID. @DTS Engineer could the registration for app.blacksands.southislandguide be checked? No client-side changes pending on our side.