From debecf3921d42c462c72ac8fd2a29ce1193dd8ba Mon Sep 17 00:00:00 2001
From: Chris Chinchilla <chris.ward@supabase.io>
Date: Tue, 10 Mar 2026 17:06:22 +0100
Subject: [PATCH] docs: SwitchGoogle social auth to getClaims (#43593)

## I have read the
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
file.

YES
---
 apps/docs/content/guides/auth/social-login/auth-google.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/apps/docs/content/guides/auth/social-login/auth-google.mdx b/apps/docs/content/guides/auth/social-login/auth-google.mdx
index dfd3aebff5c..805fb928713 100644
--- a/apps/docs/content/guides/auth/social-login/auth-google.mdx
+++ b/apps/docs/content/guides/auth/social-login/auth-google.mdx
@@ -395,11 +395,11 @@ const OneTapComponent = () => {
     console.log('Nonce: ', nonce, hashedNonce)
 
     // check if there's already an existing session before initializing the one-tap UI
-    const { data, error } = await supabase.auth.getSession()
+    const { data: { claims }, error } = await supabase.auth.getClaims()
     if (error) {
-      console.error('Error getting session', error)
+      console.error('Error getting claims', error)
     }
-    if (data.session) {
+    if (claims) {
       router.push('/')
       return
     }