Adding another recent data point for this thread — Team U3KSLBV22Q, Bundle ID com.yyssd, same AKAuthenticationError -7003 / ASAuthorizationError 1001 pattern. Feedback ID: FB23839261 The akd log shows the deeper SRP failure chain (with AuthKit profile installed): Encountered error while fetching developer team: AKSQLError -6003 No applications were found with the provided Client ID Using personal credential state - 2, error - AKAuthenticationError -7074 setError: 2:M2 missing (bad password) SRP authentication with server failed! Error performing auth request: AKAuthenticationError -7003 The AKSQLError -6003 and M2 missing (bad password) combo is significant — it suggests Apple's backend can't find the App ID → team mapping for com.yyssd in the SIWA provisioning database, so the SRP handshake fails with a phantom "bad password" error even though the user's Apple ID password is correct (Face ID succeeded). Has anyone seen this resolved after waiting? We've already waited >48h since the capability was last recreated.

Same exact failure signature here, on Team U3KSLBV22Q, Bundle ID com.yyssd. Feedback ID: FB23839261 Captured sysdiagnose with AuthKit profile installed, the akd failure chain is identical to the original report: akd: [authkit:siwa] Encountered error while fetching developer team: Error Domain=AKSQLError Code=-6003 akd: [authkit:siwa] No applications were found with the provided Client ID: akd: [authkit:siwa] Using personal credential state - 2, error - AKAuthenticationError Code=-7074 akd: [authkit:core] Performing SRP request with context akd: [AppleIDAuthSupport] setError: 2:M2 missing (bad password) akd: [authkit:core] SRP authentication with server failed! akd: [authkit:siwa] Error performing auth request: AKAuthenticationError Code=-7003 What we've exhaustively verified (all PASS): SIWA capability enabled on App ID via App Store Connect API (APPLE_ID_AUTH + PRIMARY_APP_CONSENT) Tried deleting and recreating the capability via API — same failure com.apple.developer.applesignin present in entitlements and embedded provisioning profile (verified via security cms -D) iOS 26.5.2 (23F84) — production, not beta Tried two different Apple IDs — both fail identically Tried deleting app + "Reset Location & Privacy" — same failure No prefix conflict (removed SIWA from sibling App ID com.yyssd.game) — same failure App Store Connect API shows the App ID is registered correctly Control test that WORKS: on the same iPhone 13, with the same Apple ID, at the same time, SIWA in App Store apps from other teams (Notion etc.) completes without issue. The failure is therefore strictly scoped to Team U3KSLBV22Q. The AKSQLError -6003 "No applications were found with the provided Client ID" line from akd is the smoking gun — Apple's backend does not recognize com.yyssd as having SIWA enabled, despite the App Store Connect API showing otherwise. Happy to share the full sysdiagnose logarchive via DTS. Please advise on next steps to get the team's SIWA provisioning re-initialized server-side.