I'm developing a Unity iOS app using the official "Sign In with Apple" Unity plugin (v1.5.0), and I'm encountering persistent errors during authentication. Here’s the full context:
App Info:
Unity version: 6000.0.32f1
Bundle ID: com.pfcgaming.applesignin
Sign In with Apple enabled in the Apple Developer portal
Real iOS device, not simulator
Error Logs:
txt Copy Edit Authorization failed: Error Domain=AKAuthenticationError Code=-7003 "(null)" UserInfo={AKClientBundleID=com.pfcgaming.applesignin}
ASAuthorizationController credential request failed with error: Error Domain=com.apple.AuthenticationServices.AuthorizationError Code=1001 "(null)"
Description: The operation couldn’t be completed. No credentials available for login. What I’ve Done So Far:
Verified "Sign In with Apple" is enabled under the App ID in developer.apple.com.
Provisioning profile has been regenerated with correct entitlements.
Xcode project has the “Sign In with Apple” capability added.
Tested on multiple real iOS devices with iCloud + Keychain enabled.
Tried both PerformQuickLogin() and LoginWithAppleId() approaches in the plugin.
My Observations:
These errors started occurring right after enabling "Sign In with Apple" in the developer portal.
Based on some community feedback, there may be a backend propagation delay after enabling SIWA (Sign In With Apple) which might cause these errors.
Questions:
Is it expected to receive error -7003 or 1001 immediately after enabling SIWA in the Developer Portal?
How long does it typically take for entitlement changes to fully propagate?
Is there any Apple-recommended workaround to test during this wait time?
Any insight or confirmation would be helpful. Thanks in advance!
Hi @SomendraShah,
You wrote:
Is it expected to receive error -7003 or 1001 immediately after enabling SIWA in the Developer Portal?
Yes, both errors are expected transiently. However, they are symptoms of propagation delay not permanent failures.
The -7003 error can occur when the authentication backend does not yet recognize your App ID as having the Sign in with Apple entitlement. It can also occur if your provisioning profile hasn't been regenerated after enabling Sign in with Apple for your app.
The 1001 error usually represents a user-initiated cancellation of the Sign in with Apple auth flow, but immediately after enabling Sign in with Apple, it is almost always a system-initial cancellation due to the underlying -7003 error. The Sign in with Apple auth sheet silently fails to present and the system auto-dismisses, reporting it as a cancellation.
Next, you wrote:
How long does it typically take for entitlement changes to fully propagate?
There is no official time range I can provide for this scenario. However, the best case I'd suggest is within 15 min, and the worse case could potentially be up to 24 hours.
Then, you wrote:
Is there any Apple-recommended workaround to test during this wait time?
- Verify the Sign in with Apple entitlement is in your
.entitlementsfile. - Regenerate all provisioning profiles linked to your App ID.
- Re-download profiles in Xcode.
- Clean build, to perform a fresh install on a physical device.
- Confirm the entitlement is embedded in your signed binary:
codesign -d --entitlements :- /path/to/YourApp.app
For the quickest approach, do the following:
- Enable Sign in with Apple in the App ID configuration on the Developer portal.
- Add the Sign in with Apple capability in Xcode's Signing & Capabilities tab.
- Clean build.
- Run app.
Most developers find this resolves the issue in under 5 minutes.
Cheers,
Paris X Pinkney | WWDR | DTS Engineer
