---
title: "Native Mobile Auth Support for Google and Apple Sign in"
description: "Supabase has expanded its authentication support for native Apple and Google sign-in on iOS and Android, addressing a flow that previously required developers to send users through a web browser. Native apps built with Flutter or React Native can use OS-provided authentication dialogs across Apple platforms including iOS, macOS, tvOS, and watchOS, while Android support covers all Android variants. Behind these methods, ID tokens issued by Apple or Google are validated by Supabase Auth to create accounts or link existing accounts based on email similarity. The same signInWithIdToken() method also enables Sign in with Apple JS, Google One Tap, and authentication in Chrome extensions; the Google One Tap example passes the provider’s credential and a matching nonce when one is supplied via data-nonce."
---

# Native Mobile Auth Support for Google and Apple Sign in

[Supabase](https://yomu.fyi/company/supabase) · stojan,tyler\_shukert · Jun 27, 2023

**Type:** Announcement

## Summary

Supabase has expanded its authentication support for native Apple and Google sign-in on iOS and Android, addressing a flow that previously required developers to send users through a web browser. Native apps built with Flutter or React Native can use OS-provided authentication dialogs across Apple platforms including iOS, macOS, tvOS, and watchOS, while Android support covers all Android variants. Behind these methods, ID tokens issued by Apple or Google are validated by Supabase Auth to create accounts or link existing accounts based on email similarity. The same signInWithIdToken() method also enables Sign in with Apple JS, Google One Tap, and authentication in Chrome extensions; the Google One Tap example passes the provider’s credential and a matching nonce when one is supplied via data-nonce.

## Context

Native mobile applications previously required developers to use a web browser for OAuth sign-in, which was described as an unsuitable user flow when operating-system authentication dialogs were available. Existing native support also had edge cases that Supabase Auth did not cover well.

## Approach / What changed

Supabase added supported native Sign in with Apple and Google flows using provider-issued ID tokens. Supabase Auth validates those tokens and creates or links accounts based on email similarity. The signInWithIdToken() method also accepts tokens from Sign in with Apple JS, Google One Tap, and Chrome extension authentication flows.

## Takeaways

- Native Apple and Google authentication is supported for iOS, macOS, tvOS, watchOS, and all Android variants, including apps built with Flutter or React Native.
- Apple and Google native sign-in methods provide ID tokens that Supabase Auth validates before creating or linking user accounts based on email similarity.
- The signInWithIdToken() method supports Google One Tap, Sign in with Apple JS, and Chrome extensions; Google One Tap requires a matching nonce when one is supplied through data-nonce.

**Tags:** [Android](https://yomu.fyi/topic/android), [Authentication](https://yomu.fyi/topic/authentication), [Developer Experience](https://yomu.fyi/topic/developer-experience), [iOS](https://yomu.fyi/topic/ios)

- Source: [Supabase](https://supabase.com/blog/native-mobile-auth)
- Source URL: https://supabase.com/blog/native-mobile-auth
- Ingested by Yomu: 2026-08-29T01:18:28.603Z

[Read original post](https://supabase.com/blog/native-mobile-auth)