---
title: "Comment by ephilo on \"Google authentication with Expo & Supabase\" | Hashnode"
description: "This article was a shining gem in a lake of information. I didn&#39;t have a proper guide to help me integrate expo with supabase and get a google login, but th"
url: "https://hashnode.com/posts/google-authentication-with-expo-supabase/6479c97a18e273fbcfbe88e6/comment/647ee3ea1147de02efa76518"
---

[Discussion](https://hashnode.com/posts/google-authentication-with-expo-supabase/6479c97a18e273fbcfbe88e6)

Comment [Google authentication with Expo & Supabase](https://hashnode.com/posts/google-authentication-with-expo-supabase/6479c97a18e273fbcfbe88e6)

[ephilo](https://hashnode.com/@ephilo)

[Jun 6, 2023](https://hashnode.com/posts/google-authentication-with-expo-supabase/6479c97a18e273fbcfbe88e6/comment/647ee3ea1147de02efa76518)

This article was a shining gem in a lake of information. I didn't have a proper guide to help me integrate expo with supabase and get a google login, but this article made it easy. Thank you so much. However, when I logged in with google, I get the following warning statement, did you ever have this problem?

// Warning Provided value to SecureStore is larger than 2048 bytes. An attempt to store such a value will throw an error in SDK 35.

I used below code.

// Code SecureStore.setItemAsync( "google-access-token", JSON.stringify(data.provider\_token) );

Actually, I don't think this code is affecting anything, but in the supabase function I create with createClient, I'm assigning an ExpoSecureStorageAdapter to auth.storage, and I'm wondering if I'm settingItem to all the data that is automatically handed over by google.

[Mauro Garcia](https://hashnode.com/@mauro-codes)

[Jun 6, 2023](https://hashnode.com/posts/google-authentication-with-expo-supabase/6479c97a18e273fbcfbe88e6/comment/647ee3ea1147de02efa76518#reply-647f18471147de02efa76d32)

Hey! Thanks for the comment! I'm glad to hear that the article was helpful :)

I saw the warning you mentioned, but I got that warning while trying to store the entire "data" object. Based on what I've read, I think the ExpoSecureStorageAdapter will save the access token, refresh token, and other info, but I'm not sure if the provider token is being stored for security reasons.

Will take a look at this later and come back with a reply if I find new info. Thanks for the heads-up!

[ephilo](https://hashnode.com/@ephilo)

[Jun 7, 2023](https://hashnode.com/posts/google-authentication-with-expo-supabase/6479c97a18e273fbcfbe88e6/comment/647ee3ea1147de02efa76518#reply-647fdb057fef2032a2441ec4)

[Mauro Garcia](https://hashnode.com/@mauro-codes) Thank you very much, Mauro :)
