Native Google ID token fails Supabase nonce check
Native iOS Google sign-in through Supabase signInWithIdToken or linkIdentity({provider:'google', token}) gets a 400 on /token (grant_type id_token) with the error invalid request: Passed nonce and nonce in id_token should either both exist or not. Google's native SDK puts a nonce claim in the ID token, but @react-native-google-signin/google-signin v16.1.4 cannot accept or return a nonce, so the client has nothing to send. Apple native sign-in without a nonce works because Apple's token has no nonce claim. Don't assume what works for Apple will work for Google. The fix that needs no new build is to turn on Dashboard → Auth → Providers → Google → 'Skip nonce checks'. This weakens replay protection, though the aud and expiry checks still apply.
Checked in source (GoogleSignIn-iOS 9.1.0 with AppAuth-iOS 2.0.0): when no custom nonce is passed, GIDSignIn builds its OIDAuthorizationRequest with the AppAuth initializer that generates a random nonce itself (OIDAuthorizationRequest.m: nonce:[[self class] generateState]), so every native Google ID token carries a nonce the app never saw. GoogleSignIn 9.0.0+ takes a custom nonce (signInWithPresentingViewController:hint:additionalScopes:nonce:), so a native SDK client can pass a server-issued nonce instead of turning the check off. Note GoogleSignIn 10.x (Sept 2026) needs Xcode 27 and iOS 15+.