iOS

Sign in with Apple for web apps: when you need it and how to add it

November 17, 2026 · 6 min read

Illustration of a phone sign-in screen with an Apple-style sign-in button

If your iPhone app offers Google or another social login, Apple usually requires Sign in with Apple as well. If you only offer email and password, you do not need it.

That rule comes from Apple's guideline 4.8, and it has clear exceptions. Below you will find when it applies, what to set up in your Apple account, and how to add it to a Supabase or Lovable app.

What to expect
Reading time: about 6 minutes. Setup usually takes a few hours if your sign-in runs on Supabase or a similar service. You need a paid Apple Developer account. PWAtoApp builds your app, but sign-in is set up in your web app and your Apple account.

The rule in plain words

Guideline 4.8 covers login services. It says that if your app offers a third-party or social login, such as Google or Facebook, it must also offer an equivalent login that protects privacy.

That equivalent must limit the data collected to name and email, let users hide their email address, and not track users for ads without consent. Sign in with Apple meets all three, which is why it is the usual choice. The full text is in the App Store Review Guidelines.

When you do not need it

The rule does not apply everywhere, because Apple lists several exceptions. The most common ones are:

  • Your app only uses your own email and password sign-in.
  • Your app is for education or business, and users sign in with an existing school or company account.
  • Users sign in with a government or industry ID system.
  • Your app is a client for a specific third-party service, and users sign in to that service directly.

The first exception is the simplest path: with only email and password, you need no Sign in with Apple. It is also the login least likely to break in a mobile app.

What you need to set up

If the rule does apply, setup has four parts. Their names sound technical, but each one is a form in your Apple Developer account.

  • An App ID with the Sign in with Apple capability turned on.
  • A Services ID. This is the identifier your website uses for Apple sign-in.
  • A return URL. Apple sends users back here after they sign in. With Supabase, it is the callback URL shown in your Supabase Auth settings.
  • A private key (a .p8 file). Your sign-in service uses it to talk to Apple. Store it safely.

Adding it with Supabase or Lovable

With those parts ready, you connect them to your sign-in service. Most Lovable apps use Supabase, which supports Apple as a provider: you turn it on in the Auth settings and paste in the details from your Apple account.

Then add a Sign in with Apple button to your sign-in screen, which Lovable can do from a prompt. Apple has design rules for the button, so use the official style and wording.

Watch the expiry date
With the web sign-in flow, Supabase asks for a secret created from your Apple key. That secret expires after at most 6 months. Put a reminder in your calendar to renew it, or Apple sign-in will stop working.

Hidden email addresses

When users sign in with Apple, they can choose to hide their real email. Apple then gives you a private relay address that forwards to them.

Because of that relay, any email your app sends, such as receipts or password resets, must come from a domain you have registered in your Apple Developer account. Otherwise, emails to relay addresses may not arrive.

Test it before you submit

  • Sign in with Apple on a real iPhone in your app, not only on the website.
  • Try both options: share your email and hide your email.
  • Sign out and sign in again. You should reach the same account.
  • Check that sign-in returns to the app, not to the browser.

If sign-in leaves the app during these tests, read how to fix login in a Lovable mobile app. For a full test round with other people, use TestFlight.

Where PWAtoApp fits

PWAtoApp turns your web app into a signed iOS IPA and Android builds for €49.99 once, with unlimited builds. Sign in with Apple lives in your web app and your Apple account, so you add it there, then rebuild and test. Because missing Apple sign-in is a common rejection reason, also see why Apple rejects wrapped web apps.

FAQ

Do I need Sign in with Apple on Android too?

No. The rule is Apple's, for the App Store. You can still offer it on Android or the web if you want the same options everywhere.

Can users who signed up with Google switch to Apple?

Only if your app links accounts. Without that, signing in with Apple creates a new account. Plan how you will handle this before launch.

Does Sign in with Apple cost extra?

No. It is included in the Apple Developer Program membership.

Ready to build for Android and iOS?

€49.99 once includes unlimited Android APK and AAB plus iOS IPA builds, all from one dashboard.

Build my app