Same signature — adding a tenth team. Team ID: UYF568NSN7 Capability enabled 16 July 2026, "Enable as a primary App ID", nothing grouped Native ASAuthorizationAppleIDProvider via expo-apple-authentication, TestFlight iPhone 15 Pro and iPad, both iOS 26.5 (23F77) Feedback: FB24273454 (sysdiagnose, screen recording, App ID configuration) Sheet presents and names the app, Face ID succeeds, then "Sign Up Not Completed". No ASAuthorizationAppleIDCredential returned; nothing reaches our backend. It has never completed a single authorization since the capability was enabled. sysdiagnose captured within a minute of a reproduction (11 Aug 2026, 11:35 EDT) carries the same akd signature reported above: AppleIDAuthSupport Code=2 / -7003 "M2 missing (bad password)" during the SRP request Ruled out on our side: Same Apple ID creates a first-time Sign in with Apple association in an unrelated App Store app minutes later, same device, same network. A second, different Apple ID fails identically in our app. A second device (iPad, never previously installed) fails identically. Entitlement present in the provisioning profile AND claimed in the signed binary: com.apple.developer.applesignin = ["Default"]. A build requesting a capability the App ID lacks was refused at signing, so the pipeline does enforce capabilities. Configuration deliberately frozen — no capability toggles — so the failing state is preserved for inspection. Guideline 2.1(a) rejections reported above by other teams are our live risk.