"Sign Up Not Completed" Error When Using Sign In with Apple on Real Device

Question

Jinsss OP

Created Jun ’25

Replies 4

Boosts 1

Participants 4

Hello,

I'm developing an iOS app that includes a Sign In with Apple feature. I’ve completed the following setup steps:

Enabled Sign In with Apple for the app’s Bundle ID in the Apple Developer Console.
Added Sign In with Apple capability in Xcode under Signing & Capabilities.
Tested the feature on a real device, not a simulator.
Registered the real device ID in the Developer Console just in case any hidden permission issues exist.

Despite following all the necessary steps (and even using the official Apple sample code) the Sign In bottom sheet displays a "Sign Up Not Completed" message. Unfortunately, I don’t receive any further error details to help diagnose the issue.

After searching through StackOverflow and this forum, I came across posts suggesting that the feature might take up to 48 hours to become active after setup. Is this still the case in 2025? Or is there something I might be missing?

For additional context: other features such as APNs (Push Notifications) are working as expected.

Thank you in advance for any help or insight!

Answered by Jinsss in 846358022

I didn't change anything, but after about two days, it suddenly started working as expected. It seems like there might be some server-side propagation or activation delay on Apple's end. Just leaving this here in case someone else runs into the same issue.

Boost

Answer 1

__carter OP

Jun ’25

Are you on the iOS 26 beta?

0

Answer 2

debugzen OP

Jun ’25

We are facing the same problem, see this: https://developer.apple.com/forums/thread/789011

0

Answer 3

animatoinc OP

Jun ’25

also happening to us, both on iOS beta and release version

0

Answer 4

Jinsss OP

Jun ’25

Accepted Answer

I didn't change anything, but after about two days, it suddenly started working as expected. It seems like there might be some server-side propagation or activation delay on Apple's end. Just leaving this here in case someone else runs into the same issue.

0