Skip to main content
This page documents Apple authentication for your app’s users. It is available only for apps using the built-in backend. For an overview of all sign-in methods, see Users and authentication.
Let users sign in to your app with their Apple account instead of creating a password. Apple sign-in fits apps with an audience on Apple devices, and apps that already offer Google sign-in and want parity. Apple lets users hide their real email address. Your app then receives a private relay address from Apple, which forwards mail to the user’s inbox.

Choose a setup option

Users sign in the same way with both options. The options differ in who manages the credentials and what you can control.
1

Ask Lovable to add Apple sign-in

In the project chat, ask:
Lovable enables the provider in More → Users → Settings → Apple and adds the sign-in button to your app’s login page. If you enable it yourself in the same settings, Lovable sends a message to the project chat on your behalf and adds the button. That message is treated as standard build usage and consumes credits.
2

Test the flow

Verify that:
  • a Sign in with Apple button appears on your login page
  • users are redirected to Apple to confirm
  • users return to the app in a signed-in state
  • new users appear in More → Users
With Managed by Lovable, users must share an email address with your app to complete sign-in. Users who pick Apple’s Hide My Email option still provide one: Apple shares a private relay address with your app instead of the real one.

Managing Apple authentication

You can switch between Managed by Lovable and Your own credentials at any time from More → Users → Settings → Apple. Existing accounts are kept, but Apple identifies users per developer team: users who signed up under the previous mode may not be recognized when they next sign in with Apple, and Hide My Email relay addresses change with the team. Plan the switch before your app has many Apple users. To remove the sign-in option, ask Lovable in the project chat:
You can also disable the provider in the auth settings. Lovable then sends a message to the project chat on your behalf and removes the button. That message is treated as standard build usage and consumes credits. Users who signed up with Apple keep their accounts but need another enabled sign-in method to get back in.

Troubleshooting

Your client secret has probably expired. Apple limits each JWT to 6 months. Generate a new secret from your .p8 key with Generate secret and save it in the Apple auth settings.
The return URLs in your Apple Services ID configuration don’t match the redirect URLs Lovable shows. Copy every return URL from Lovable into the Apple Developer portal exactly, then retry. If sign-in fails only on your published app or custom domain, also check your project’s redirect URLs.
Apple forwards mail sent to the relay address only while the user keeps forwarding enabled. Treat the relay address like any other email in your app, and offer an in-app way for users to update their contact details.

FAQ

Only if you use your own credentials. In Managed by Lovable mode, Lovable provides the OAuth configuration and no Apple Developer account is needed.
Apple shares a private relay address with your app instead of the real one, so the user still has an email your app can use. With your own credentials, the Allow users without an email toggle additionally controls whether users can sign in without providing any address.
If you use your own credentials, the most common cause is an expired client secret: Apple limits each JWT to 6 months. Generate a new secret from your .p8 key and save it in the Apple auth settings.
No. It is an additional sign-in method, and you can offer it alongside email, Google, and other methods.
Yes, anytime from More → Users → Settings → Apple. Existing accounts are kept, but Apple identifies users per developer team, so users who signed up under the previous mode may not be recognized after the switch. Plan the switch before your app has many Apple users.
Not with Managed by Lovable. In that mode, Lovable signs people in with its own Apple identifiers, so your project’s backend does not accept a token that Apple issues to your iOS app. With your own credentials, Client ID takes one identifier: your Services ID for sign-in in the browser, or the app’s Bundle ID for native sign-in in the iOS app.To sign people in from the iOS app, have it open Sign in with Apple in the browser. Add the app’s custom scheme, such as myapp://callback, to Redirect URLs in the auth settings. See Site URL and redirect URLs.
No. Sign in with Apple works in any browser. Users sign in with their Apple Account credentials, and users on Apple devices get the smoothest flow.