Adding another affected team, plus a server-side transaction ID that may help triage. Team ID: 3255U9X75G App ID: com.nazacheres.wbando (also com.nazacheres.wbando.dev - the team's only two identifiers, both APPLE_ID_AUTH / PRIMARY_APP_CONSENT) Feedback Assistant: FB24238948 (sysdiagnose with the Accounts/AuthKit profile attached). Developer Support case: 20000135878194. Capability enabled 2026-08-05; failing since 2026-08-06; still failing 2026-08-12. Same signature as the rest of the thread - the sheet renders, authentication succeeds, "Sign Up Not Completed", ASAuthorizationError 1001 with null userInfo, and in akd: Encountered error while fetching developer team: Error Domain=AKSQLError Code=-6003, then No applications were found with the provided Client ID. One detail I have not seen posted yet: with the Accounts/AuthKit profile installed, the GSA response body is readable and carries Apple's own transaction identifier. Captured 2026-08-09 23:28:09 CEST: ec = "-24009"; ed = ""; em = "Invalid client."; hsc = 200; ptxid = "1b7e78e3-79da-4861-8f3b-23c9a2d14bd8"; followed by AppleIDAuthSupport: setError: 2:M2 missing (bad password) and SRP authentication with server failed! (com.apple.AppleIDAuthSupport Code=2). That ptxid should let someone at Apple pull this exact rejection from the server side rather than inferring it from client logs. Note the code here is -24009 rather than the -24000 reported by moty66 and DanCue - same "Invalid client." message, so these look like variants of the same registration failure. Client side verified the same way as everyone else in this thread: APPLE_ID_AUTH / PRIMARY_APP_CONSENT read back from the App Store Connect API, com.apple.developer.applesignin present in both the signed binary and the embedded provisioning profile, no app extensions, no wildcard or grouped identifiers, no pending agreements, and the same Apple Accounts sign in fine to other teams' apps on the same devices. Reproduces on physical iPhones for external TestFlight testers and on an Apple Silicon Mac running the same build. Paris X Pinkney - could the same server-side team registration fix be applied to 3255U9X75G? Happy to re-test and confirm immediately. Also confirming permsdenied's reading of 4.8 for anyone else weighing options: we are taking the same route and shipping without Google Sign-In so the guideline no longer applies, rather than waiting on the fix.