Annoying supabase message "This generation uses Supabase"

Feedback
,
1

I’ve integrated Supabase by correctly setting NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY in my .env file. I also used V0 to handle the integration. Everything seems to be working—my Supabase setup and V0-generated project are functioning as expected.

However, every time I open the V0 interface, I keep getting an annoying popup that says:

This generation uses Supabase.

Add the required integration in chat or from the Settings panel.

Open Settings

I’ve already opened the Settings panel and confirmed that Supabase is properly configured. I even reapplied the .env file and asked V0 to verify the integration—it confirmed everything is fine. Still, the modal keeps showing up.

This is really frustrating and a huge time sink. Everything is working, but the persistent modal won’t go away, and I can’t figure out why.

This photo V0 says that everything is correctly mapped:

image
image419×804 57.7 KB

This one is the annoying popup

image
image486×448 14.9 KB

If this is due to a limitation in detecting Supabase integrations outside of Vercel, that’s understandable. But in that case, please consider adding a “Dismiss” or “Ignore” option so this doesn’t block the workflow unnecessarily.

2

It sounds like the integration isn’t fully connected yet. What do you see when you click the “Open Settings” button?

3

image
image958×991 58.2 KB

The v0 wants me to create a new supabase. But I already have one outside vercel (directly on supabase)

4

Would you be able to share a link to the chat or just the chat id? That’ll let me dig into the logs for more info about why this is happening

5

Is this link enough?
https://v0.dev/chat/stripe-wip-HbSj8dNTMq4

6

That’s perfect. Looking into it now. I’ve asked the team for advice as well, and I’ll let you know when I learn more

7

I am also getting this issue. Sometimes it decides to work and sometime it doesn’t and I’m not changing anything.

8

Hi, i’m wondering did you get to the stage where you put some of the api code or the code that helps talk from your site to the database at all?

If so, could be worth checking if any of that code is still in there that’s causing it.