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
Same issue for our team — and the flow has never once succeeded, starting from our very first attempt. Team ID: AJ36Q485L4 (Individual, enrolled August 2026). Client ID / bundle: com.tcndtht.outpawtient (the team's only App ID, APPLE_ID_AUTH enabled as primary App ID). The signature matches this thread exactly: the sheet renders fully, Face ID succeeds, then "Sign-Up not completed"; zero requests reach our backend. Two different personal Apple Accounts (2FA) on two different iPhones; Sign in with Apple works in other apps on the same devices at the same minute. Entitlement verified in the signed binary and embedded profile; agreements accepted; removing and re-adding the capability on 23 Aug 2026 (profile reissued) changed nothing. The public authorize endpoint returns a bare 403 Forbidden for our client_id — identical to a nonexistent client — while a known-good client id from the same network renders the normal sign-in page. Filed as FB24490686. We would appreciate the same server-side registration fix being applied to our team.
1w
Reply to Sign in with Apple: "Sign Up Not Completed" for every App ID in our team — framework returns canceled (1001) with empty userInfo
Same issue for our team — and the flow has never once succeeded, starting from our very first attempt. Team ID: AJ36Q485L4 (Individual, enrolled August 2026). Client ID / bundle: com.tcndtht.outpawtient (the team's only App ID, APPLE_ID_AUTH enabled as primary App ID). The signature matches this thread exactly: the sheet renders fully, Face ID succeeds, then "Sign-Up not completed"; zero requests reach our backend. Two different personal Apple Accounts (2FA) on two different iPhones; Sign in with Apple works in other apps on the same devices at the same minute. Entitlement verified in the signed binary and embedded profile; agreements accepted; removing and re-adding the capability on 23 Aug 2026 (profile reissued) changed nothing. The public authorize endpoint returns a bare 403 Forbidden for our client_id — identical to a nonexistent client — while a known-good client id from the same network renders the normal sign-in page. Filed as FB24490686. We would appreciate the same server-side registration fix being applied to our team.
Replies
Boosts
Views
Activity
1w