Post

Replies

Boosts

Views

Activity

Reply to Sign in with Apple: "Sign Up Not Completed" for every App ID in our team — framework returns canceled (1001) with empty userInfo
Team W4LV5W25SX — same fingerprint, adding us to the list. FB24668445 Sheet authenticates, then "Sign Up Not Completed"; the framework returns AuthorizationError code 1001 with an EMPTY userInfo and nothing ever reaches our server (verified as zero rows in both our staging and production databases since 22 Aug 2026). All three of our App IDs fail, including a MINIMAL CONTROL APP — one view, one ASAuthorizationAppleIDButton, no networking, no server, no shared code with our product, its App ID created after the failures began. It fails identically, which rules out our application code, our entitlements handling and our server. com.anralabs.lifecompass APPLE_ID_AUTH / PRIMARY_APP_CONSENT com.anralabs.lifecompass.dev APPLE_ID_AUTH / PRIMARY_APP_CONSENT com.anralabs.signinrepro APPLE_ID_AUTH / PRIMARY_APP_CONSENT Varied with no change: 3 Apple IDs (two different people), 3 devices, a development build and a TestFlight build of the production bundle, both scope combinations, fresh install after a power cycle. Sign in with Apple works normally in third-party apps on the same devices with the same Apple IDs. Capability, seedId and the applesignin entitlement are verified correct in the signed binary and the embedded profile. One data point on the pattern several of you have noticed: all three of our App IDs were registered on 22 August 2026, and we have NONE predating that. That is consistent with the reports here of an older App ID still working while a newly registered one in the same team fails — it would explain why every one of ours fails rather than just some. We have deliberately not toggled the capability, regenerated profiles or recreated App IDs, since those were reported here as making no difference and we would rather preserve the state for inspection. DTS code-level request opened 25 Aug 2026; only the automated acknowledgement so far. Our own thread: https://developer.apple.com/forums/thread/844736 Requesting the same server-side re-registration that resolved GW7XA5CX69 and FRL3DTJQ62.
Sep ’26
Reply to Sign in with Apple: "Sign Up Not Completed" for every App ID in our team — framework returns canceled (1001) with empty userInfo
Team W4LV5W25SX — same fingerprint, adding us to the list. FB24668445 Sheet authenticates, then "Sign Up Not Completed"; the framework returns AuthorizationError code 1001 with an EMPTY userInfo and nothing ever reaches our server (verified as zero rows in both our staging and production databases since 22 Aug 2026). All three of our App IDs fail, including a MINIMAL CONTROL APP — one view, one ASAuthorizationAppleIDButton, no networking, no server, no shared code with our product, its App ID created after the failures began. It fails identically, which rules out our application code, our entitlements handling and our server. com.anralabs.lifecompass APPLE_ID_AUTH / PRIMARY_APP_CONSENT com.anralabs.lifecompass.dev APPLE_ID_AUTH / PRIMARY_APP_CONSENT com.anralabs.signinrepro APPLE_ID_AUTH / PRIMARY_APP_CONSENT Varied with no change: 3 Apple IDs (two different people), 3 devices, a development build and a TestFlight build of the production bundle, both scope combinations, fresh install after a power cycle. Sign in with Apple works normally in third-party apps on the same devices with the same Apple IDs. Capability, seedId and the applesignin entitlement are verified correct in the signed binary and the embedded profile. One data point on the pattern several of you have noticed: all three of our App IDs were registered on 22 August 2026, and we have NONE predating that. That is consistent with the reports here of an older App ID still working while a newly registered one in the same team fails — it would explain why every one of ours fails rather than just some. We have deliberately not toggled the capability, regenerated profiles or recreated App IDs, since those were reported here as making no difference and we would rather preserve the state for inspection. DTS code-level request opened 25 Aug 2026; only the automated acknowledgement so far. Our own thread: https://developer.apple.com/forums/thread/844736 Requesting the same server-side re-registration that resolved GW7XA5CX69 and FRL3DTJQ62.
Replies
Boosts
Views
Activity
Sep ’26