Update: Sign in with Apple is now working for us as well, and I want to confirm the fresh-provisioning-profile finding above — we're an Expo/EAS + Clerk app and hit the identical "Sign Up Not Completed" / akd SRP Code=2 failure.
Our App Store provisioning profile looked completely healthy: status Active in the Developer portal, a future expiration, and the correct com.apple.developer.applesignin = Default entitlement. Native Sign in with Apple still failed for every user and even for Apple's App Review team, while our web (Services ID) flow worked fine.
What we did — nothing but a fresh profile:
Regenerated ONLY the iOS App Store provisioning profile (via EAS), keeping the same bundle ID (com.narralife.lifestorycompiler), same team (D9A9BLNR6U), and the same distribution certificate. No new certificate.
The new profile came back ACTIVE (live from Apple's API) with the Sign in with Apple entitlement intact.
Rebuilt with the fresh profile and uploaded a new TestFlight build. No app code, no Expo apple-authentication change, no Clerk/provider change, no bundle ID change.
Result: native Sign in with Apple now completes and returns the identity token; login, onboarding, and session persistence all work.
Caveat (same as noted above): I can't prove the profile alone was the cause — Apple-side state may have changed or propagated during the same window. But regenerating the profile is the only thing we changed, so for anyone still stuck on Expo/EAS, generating a fresh App Store provisioning profile and rebuilding is worth trying. Feedback filed as FB24774025.
Topic:
Privacy & Security
SubTopic:
Sign in with Apple
Tags: