Hi!
I’ve implemented Google Auth using Supabase and it works super well.
Unfortunately it only works on my production environment, which is pretty annoying as I then have to deploy every time I make changes to the code to test anything.
It comes with this error:
How can I fix this? 
Is this the same issue?
Yes - I have tried using the link from the preview new tab window in the Google Cloud console, but it doesn’t work. Also, that link is dynamically so it wouldn’t be a viable solution anyway. Here’s how my Google Cloud is setup:
@pawlean This is really unfortunate and affects any Google auth implementation, including Supabase and Firebase. Some sort of complicated proxy-based auth flow would have to be created by the user, which defeats the underlying purpose of v0. It seems like the only viable solution would be to change v0 to make preview domains stable within a project.
ex: https://preview-myapp-kzmw0kj91pc72h6i4fnr.vusercontent.net/v195/....
Does v0 have plans to address this?
Yeah its super important.
Otherwise it will continuously be very difficult for people to develop complex products with v0, as they almost always require login.
We do have plans to make the iframe domain stable, no ETA on it unfortunately
This template uses NeonAuth, which supports both social and username/password auth. Their social auth features don’t work at all in iframes (restriction on their end) but the username/password does so I use that when I’m inside v0 and social when I’m outside of it. You may be able to do the same with your supabase auth
Sounds good - will look into that. Thanks, Jacob!
