Team SW8F94Y42Y (com.homyaid.app): still failing as of 2026-10-19, now about 4 weeks after FB24922696. The public authorize endpoint still returns invalid_client for our client ID. We also opened Developer Support case 103001479183. @Paris X Pinkney, could you please check whether FB24922696 is routed to the team doing the server-side registration repairs? Thank you.

We are affected by the same issue. Team ID: SW8F94Y42Y Bundle ID: com.homyaid.app (App Store Connect app 6781570051, TestFlight) Symptoms identical to the reports above: the native Sign in with Apple sheet appears, Face ID completes, then "Sign-Up Not Completed" is shown and ASAuthorizationController returns error 1000 (.unknown) with no credential. No request ever reaches our servers. Reproduces 100% on real devices and simulator, across multiple days. Client side is fully verified: com.apple.developer.applesignin = ["Default"] is present in the signed binary's entitlements, the distribution profile is ACTIVE, the App ID has APPLE_ID_AUTH enabled as PRIMARY_APP_CONSENT (checked via the App Store Connect API), and the Program License Agreement was accepted on September 20, 2026 - the failure persisted unchanged for 3+ days after acceptance. Server-side evidence matching this thread: https://appleid.apple.com/auth/authorize?client_id=com.homyaid.app&... returns {"errorCode":"invalid_client","errorMessage":"Invalid client."} - the same response as a nonexistent client_id, while a known-working SIWA app queried with the identical request shape returns invalid_request (redirect URL) instead. Our App ID appears to be missing from the SIWA backend registration despite correct portal configuration. Filed as FB24922696 with a sysdiagnose from an affected iPhone 17 attached. Could this team/App ID be included in the server-side re-provisioning? Happy to provide akd logs if useful.