I spent two hours debugging an empty production list. The data was in the test database the whole time.

If you're building with Lovable and Supabase, there's a gotcha that will bite you eventually — and when it does, you'll wonder why nobody warned you. Consider this your warning.

The setup nobody explains

When you spin up a Supabase project through Lovable, you get two database environments: test and live . This makes sense in theory — you don't want your AI-assisted edits touching production data while you're experimenting.

The problem? The boundary between these two is almost invisible.

When you use the AI chat in Lovable to insert data — say, seed some blog posts, add sample users, or populate a lookup table — that data goes into the test database . Your production app, the one your users actually visit, reads from the live database .

You insert ten records. You check the app. Zero records.…