Skip to main content
Let people sign in to your iOS or Android app with their Google or Apple account. Both work through the same sign-in pages your app already has, so once a provider is set up the button shows up on mobile and web together. This page covers Google and Apple on mobile. For the email and password basics, protected pages, and how sessions work, see User Accounts.
Sign in with Apple is required by Apple’s App Store guidelines if your iOS app offers any other social login (like Google). If you add Google to a mobile app, add Apple too, or your build can be rejected during App Store review.

​
How it works on mobile

Your mobile app opens a sign-in screen that loads your app’s hosted sign-in page. The Google and Apple buttons live on that page, so the flow is the same one your web app uses. You don’t wire up any native SDKs or device-specific code. Set the provider up once and Anything renders the button everywhere. When you test inside the builder, the sign-in page shows up as a web page inside a preview. That’s expected. It works as a normal native screen once the app is running on a real device.

​
Before you start

An Anything project with User Accounts turned on
Your app published, or running on a preview domain you can test against
A developer account with the provider: a Google account for Google, an Apple Developer account for Apple

​
Sign in with Google

You create OAuth credentials in Google, then paste them into your project. The setup is the same as web, so follow the full walkthrough and the mobile button comes along automatically.
1

Create Google credentials

Follow the Google Sign In guide to create a project in Google Cloud, set up the OAuth consent screen, and generate a Client ID and Client Secret.
2

Add the redirect URL

In your Google OAuth client, add this as an authorized redirect URL, replacing the host with your app’s domain (your published domain in production, or your preview domain to test in the builder):
3

Enable Google in Project Settings

Open the 3-dot menu > Project Settings > Authentication, expand Google, turn it on, and paste in your Client ID and Client Secret. Save.
4

Add the button

Back in chat, say “add Google sign in as an option.” Anything updates your sign-in and sign-up pages with the Google button. It shows up on both mobile and web.
5

Publish and test

Publish, open your app, and run through the Google flow. Check the auth_users table to confirm the account was created.

​
Sign in with Apple

Apple uses four pieces of credential instead of a single client ID and secret. You generate them in your Apple Developer account.
1

Create a Services ID

In the Apple Developer portal, create a Services ID. This is your Apple Client ID. Enable “Sign in with Apple” on it.
2

Add the redirect URL

While configuring the Services ID, add this as a Return URL, replacing the host with your app’s domain (your published domain in production, or your preview domain to test in the builder):
Apple requires https and a reachable domain. You can’t use a local address, and the domain has to match the one your app is served from.
3

Create a sign-in key

Under Keys, create a new key with “Sign in with Apple” enabled. Download the .p8 private key file. You only get to download it once, so keep it safe. Note the Key ID shown next to it.
4

Find your Team ID

Your Team ID is in the top right of the Apple Developer portal, under your account membership details.
5

Enable Apple in Project Settings

Open the 3-dot menu > Project Settings > Authentication, expand Apple, turn it on, and fill in:Save.
6

Add the button

Back in chat, say “add Sign in with Apple as an option.” Anything updates your sign-in and sign-up pages with the Apple button on mobile and web.
7

Publish and test

Publish, open your app, and run through the Apple flow. Check the auth_users table to confirm the account was created.
Apple only sends a person’s name on their first sign-in, and they can choose to hide their real email behind a private relay address. Don’t assume you’ll get a name or a reachable email on every sign-in. Collect anything else you need in an onboarding step after the account is created.

​
Testing

  1. Publish your changes, or use your preview domain
  2. Open your app on a device or in Expo Go
  3. Tap the Google or Apple button on the sign-in screen and finish the flow
  4. Check the auth_users table to see the new user

​
Troubleshooting

  • Confirm User Accounts is on
  • Confirm the provider is enabled in Project Settings > Authentication
  • Re-publish, then reload the app
That’s expected. Sign-in renders as a web page inside the builder preview and works as a normal screen once the app runs on a device.
  • Check the redirect URL exactly matches https://<your-app-domain>/api/auth/callback/google or .../apple
  • Make sure the host is your real app domain, not a local address
  • For Apple, confirm the Return URL on the Services ID matches
If your iOS app has Google (or any other social login) but not Apple, App Store review can reject it. Add Sign in with Apple and re-submit.

​
See also

User Accounts

Email, sessions, protected pages

Google Sign In

Full Google credential setup

Verify Apple developer account

Get your Apple account ready

Mobile

Build and publish mobile apps