Supabase-integration per Environment is gone??? Crashing ALL my projects!

[brianostergaard]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Until today we have had supabase-integration per dev environment - “over night” it has changed without any notifications from FlutterFlow!

We have been building with FF since the start and believed in it.. but this is NOT good!

Expected Behavior

That we still have the possibility to set supabase instance per Dev environment

Steps to Reproduce

Login to a project in FF -. go to Supabase - Watch that everything is reset… .(

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

No bug code - but this is so crazy that it need to be a bug

Visual documentation

[zairzx]

Missing manual configuration fields for Supabase (Self-hosted)

After the recent FlutterFlow update, the manual input fields for "Supabase URL" and "Anon Key" have been replaced by a "Connect" button that requires OAuth authorization via the Supabase Cloud dashboard.

This change prevents configuration for projects using self-hosted Supabase instances or those running within isolated private networks (e.g., National Guard private infrastructure) where external dashboard authorization is not possible.

Furthermore, I rely on Environment Variables to toggle connection settings between Web and Private Network environments. The current "Connect" flow does not allow for this flexibility.

Could you please provide a way to manually enter these credentials or integrate Environment Variables for Supabase settings in the current UI?

[Martin-4Spaces]

We used to be able to specify the Supabase URL and anon key using environment variables.
This allowed us to have different Supabase backends for each environment.
Please restore this feature.

[sntre]

I now have this error on all the supabase actions : "Must enable database in order to define database action for progress". This is after enabling the new supabase connection. lets see

[Alezanello]

Hello,

We apologize for the inconvenience caused. We’ve recently deployed a fix—could you please check if everything is now working as expected?

Thank you!

[agreaves]

hey folks, the fix for the error on supabase actions is fixed and deployed @sntre, we're also rolling out a fix in the next hour or two to address the issue with environment specific urls and/or self-hosted Supabase (leaving an option for the existing UI). I'll update this thread once those are out as well.

Apologies, and thanks all for your patience!

[sntre]

Hello, Everything is working fine now, I’m no longer experiencing any of those errors. Thanks a lot for the quick response! Cheers, Le vendredi 20 mars 2026 à 18:25, Ale Zanello ***@***.***> a écrit :

…

Alezanello left a comment (FlutterFlow/flutterflow-issues#7009) Hello, We apologize for the inconvenience caused. We’ve recently deployed a fix—could you please check if everything is now working as expected? Thank you! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.