Apple Sign-In
The Apple Sign-In module enables native Sign in with Apple inside your iOS app. Users sign in with their Apple Account using Face ID or Touch ID — no typing, no password. Your website opens the native Apple sign-in sheet through the JavaScript Bridge and receives the user's identity token back, which your backend verifies to log the user in.
How It Works
- The user taps your website's "Sign in with Apple" button inside the iOS app.
- Your website sends an
apple_sign_inmessage to the app through the JavaScript Bridge. - The app opens the native Sign in with Apple sheet and the user confirms with Face ID, Touch ID, or their passcode.
- The app sends the user's details and identity token back to your website.
- Your website sends the identity token to its backend, which verifies it with Apple and logs the user in.
Enabling Sign In with Apple for Your App
Your app's identifier must have the Sign In with Apple capability before the native sheet can open.
- Sign in to your Apple Developer account and go to Certificates, Identifiers & Profiles → Identifiers.
- Open the identifier that matches your app's Bundle ID (shown in your Appilix dashboard).
- Under Capabilities, check Sign In with Apple and keep it as a primary App ID.
- Click Save.
- In Appilix, open the iOS Code Signing page and click Create New Provisioning Profile, so the profile includes the new capability.
- Rebuild your app.
Scopes (Optional)
The user data requested during sign-in, separated by spaces. Leave blank to use the default.
- Default:
email name - Allowed values:
email,name - Maximum length: 200 characters
Any other word is ignored, so a typo silently removes that piece of data from the request. Scopes can only be set here — they cannot be changed from the JavaScript Bridge.
What You Receive About the User
Apple handles user data differently from other sign-in providers:
- Name is only shared once. Apple returns the user's name only the first time they sign in to your app. Every later sign-in returns it empty, and the identity token never contains it — save it on your backend the first time you receive it.
- Email may be hidden. If the user chooses Hide My Email, you receive a private relay address ending in
@privaterelay.appleid.cominstead of their real email. Emails sent to it are forwarded to the user. To send emails to relay addresses, register your sending domains under Sign in with Apple for Email Communication in your Apple Developer account. - User ID is the stable identifier. The
user_idnever changes for the same user in your app. Use it, not the email, to identify returning users.
Using Sign in with Apple on Your Website Too
If your website also offers Sign in with Apple in regular browsers through a Services ID, group that Services ID with your app's App ID in your Apple Developer account. Without the grouping, Apple gives the same person a different user_id on the web and in the app, so they appear as two different users.
Triggering Sign-In from Your Website
Inside the iOS app, your website's "Sign in with Apple" button must trigger native sign-in through the JavaScript Bridge, then send the returned identity token to your backend for verification.
See Apple Sign-In JS Bridge for the code, response fields, and backend verification examples.
App Store Requirements
- Guideline 4.8: If your app offers a third-party login such as Google Sign-In, Apple requires an equivalent privacy-focused login option as well. Sign in with Apple meets this requirement.
- Guideline 5.1.1(v): If users can create an account in your app, they must also be able to delete it from within the app. For users who signed in with Apple, your backend should also revoke their Apple tokens when the account is deleted — see the Apple Sign-In JS Bridge article.