S
Supabase•9mo ago
hova

20 second call to supabase.auth.getUser()

I'm working on a minimal Supabase Auth demo app with NextJS NextJS is hosted by Vercel and Supabase is Supabase's free tier I've followed the tutorial in the docs and have a basic flow working for anonymous users. I'm noticing that any time I call supabase.auth.getUser() there's a decent chance the request is going to freeze for exactly... roughly.... 20 seconds Is this known behavior? Is this fixable via code or paying for a better tier? Anyway, the core flow is working, and I'm pretty happy with the UX but the 20s latency is nearly a dealbreaker Live site is here: https://nextjs-supabase-auth-from-scratch.vercel.app/
3 Replies
hova
hovaOP•9mo ago
Here's my logs in vercel I've consistently had it freeze up for 20 seconds Here's the code where I construct the logs https://github.com/matthova/nextjs-supabase-auth-from-scratch/blob/main/src/db/updateSessionMiddleware.ts#L33-L39
// refreshing the auth token
const beforeUser = performance.now();
const {
data: { user },
} = await supabase.auth.getUser();
const afterUser = performance.now();
console.log("Time to get user:", afterUser - beforeUser);
// refreshing the auth token
const beforeUser = performance.now();
const {
data: { user },
} = await supabase.auth.getUser();
const afterUser = performance.now();
console.log("Time to get user:", afterUser - beforeUser);
No description
Patryk
Patryk•9mo ago
I've been experiencing the same issue for the last 6 days 😫 see here: https://discord.com/channels/839993398554656828/1327609058861252609
hova
hovaOP•9mo ago
we’ve move the convo to the thread shared above 👆

Did you find this page helpful?