Bolt.new Supabase Integration - Credentials Keep Reverting to Wrong Database
Hi Supabase community,
I'm using Bolt.new (bolt.new) which has a built-in Supabase integration feature. I'm experiencing an issue where my Supabase credentials keep getting overridden.
THE SETUP:
Bolt.new offers a "Connect your existing Supabase database" feature where you provide:
- NEXT_PUBLIC_SUPABASE_URL
- NEXT_PUBLIC_SUPABASE_ANON_KEY
This is supposed to connect your Bolt project to your own Supabase instance.
THE PROBLEM:
Even after providing MY Supabase credentials (), Bolt keeps reverting to their own default Supabase instance (xowyhserzhzpvtnxuqctq.supabase.co).
WHAT HAPPENS:
1. I set my credentials in Bolt's environment variables
2. Bolt confirms: "Your key preferences have been updated"
3. Build the project
4. App connects to xowyhserzhzpvtnxuqctq.supabase.co (Bolt's database)
This happens consistently, even in new projects.
MY QUESTIONS:
1. Has anyone else experienced this with Bolt.new's Supabase integration?
2. Is there something about how Supabase connections work that would cause this auto-revert behavior?
3. Could this be related to how Bolt manages multiple Supabase instances?
4. Any workarounds from the Supabase side?
CONTEXT:
- My Supabase project: ovkzwoujdmxdvcrpoopr.supabase.co
- Using standard anon/public key from API settings
- Tables exist and have data (vendors, menu_items, etc.)
- RLS policies are configured
- Works fine when I test directly from Supabase dashboard
I've also posted in Bolt's Discord, but wondering if anyone here has insights into Supabase integration issues with third-party platforms like Bolt.
Any help appreciated!
I'm using Bolt.new (bolt.new) which has a built-in Supabase integration feature. I'm experiencing an issue where my Supabase credentials keep getting overridden.
THE SETUP:
Bolt.new offers a "Connect your existing Supabase database" feature where you provide:
- NEXT_PUBLIC_SUPABASE_URL
- NEXT_PUBLIC_SUPABASE_ANON_KEY
This is supposed to connect your Bolt project to your own Supabase instance.
THE PROBLEM:
Even after providing MY Supabase credentials (), Bolt keeps reverting to their own default Supabase instance (xowyhserzhzpvtnxuqctq.supabase.co).
WHAT HAPPENS:
1. I set my credentials in Bolt's environment variables
2. Bolt confirms: "Your key preferences have been updated"
3. Build the project
4. App connects to xowyhserzhzpvtnxuqctq.supabase.co (Bolt's database)
This happens consistently, even in new projects.
MY QUESTIONS:
1. Has anyone else experienced this with Bolt.new's Supabase integration?
2. Is there something about how Supabase connections work that would cause this auto-revert behavior?
3. Could this be related to how Bolt manages multiple Supabase instances?
4. Any workarounds from the Supabase side?
CONTEXT:
- My Supabase project: ovkzwoujdmxdvcrpoopr.supabase.co
- Using standard anon/public key from API settings
- Tables exist and have data (vendors, menu_items, etc.)
- RLS policies are configured
- Works fine when I test directly from Supabase dashboard
I've also posted in Bolt's Discord, but wondering if anyone here has insights into Supabase integration issues with third-party platforms like Bolt.
Any help appreciated!
