Sign Up Not Completed" for every new App ID on our team; older App ID works — FB23726069

Question

Created 6d

Replies 1

Boosts 0

Participants 2

Native Sign in with Apple fails with "Sign Up Not Completed" inside the AuthenticationServices sheet for every NEWLY registered App ID on our team (V4DCPCSM54) — including a clean-room probe App ID created via the ASC API with the capability enabled at creation — while an App ID registered in 2025 on the same team works. Entitlements, profiles, and capability config are all verified correct; capability toggle and fresh builds change nothing. This matches the server-side registration issue described in thread 790827.

Filed as FB[23726069] with full details. Would appreciate DTS taking a look — this is currently blocking our App Store review (rejected 2.1(a)).

Answer 1

a_tuna OP

1d

Our case supports your registration-date finding from the other direction: our entire team is new (enrolled 2026-07-13, capability first enabled 2026-07-16), so we have no pre-2026 App ID to fall back on — and every App ID of the team fails identically with "Sign Up Not Completed" / ASAuthorizationError 1001, including a clean-room probe App ID created specifically to test this. If the failure is scoped to recently-registered App IDs not propagating into the identity service, a brand-new team fails everywhere, which is exactly what we see.

Ruled out: entitlement (verified in the embedded provisioning profile), agreements (Active), scopes (unset and .fullName), signing (Xcode and TestFlight both fail), device/Apple ID (3 devices, 2 independent Apple IDs; third-party SIWA sign-ups work fine for the same Apple IDs). akd log with the Accounts profile shows the GSA sign-up SRP returning 200 with M2 missing (bad password) and null account fields — the identity server aborting the sign-up ceremony server-side.

Filed as FB23826495, referencing yours (FB23726069) and FB23716661. Precedents suggest Apple fixes this class server-side: thread 790827 (official, June 2025, 5 days) and thread 790323 (same M2 signature, 11 days).