---
title: "ephilo (@ephilo) | Hashnode"
description: "ephilo (@ephilo) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@ephilo"
---

@ephilo

# ephilo

@ephilo · Joined June 2023

## Comments

[Mauro Garcia Thank you very much, Mauro :)](https://hashnode.com/posts/google-authentication-with-expo-supabase/6479c97a18e273fbcfbe88e6/comment/647ee3ea1147de02efa76518#reply-647fdb057fef2032a2441ec4)

Reply · Article · Jun 7, 2023 · [Google authentication with Expo & Supabase](https://hashnode.com/posts/google-authentication-with-expo-supabase/6479c97a18e273fbcfbe88e6)

[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.](https://hashnode.com/posts/google-authentication-with-expo-supabase/6479c97a18e273fbcfbe88e6/comment/647ee3ea1147de02efa76518)

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