Support for Environment-Specific Supabase Project URL and API Key

[vinifcastro-inpulsah]

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

Even when using the OAuth connection, the Supabase project selection is globally applied. FlutterFlow does not detect or allow environment-specific project mapping, making it impossible to automatically switch between Dev and Prod Supabase instances when toggling environments.

Expected Behavior

FlutterFlow should allow users to map specific Supabase Projects to different App Environments (e.g., Development, Staging, and Production).

When the user switches the App Environment in the FlutterFlow settings, the corresponding Supabase project selected via the OAuth flow should automatically update to the one previously linked to that specific environment.

The integration should maintain separate Project URLs and Anon Keys (or OAuth project IDs) for each environment, ensuring that development data never leaks into production and vice versa.

If an environment is selected, the Supabase Dropdown in the integration settings should save the choice specifically for that environment.

Steps to Reproduce

Navigate to Settings and Integrations > Integrations > Supabase.

Connect your Supabase account using the OAuth login flow.

Select a specific Supabase project from the dropdown list for the current environment.

Switch the project's Environment (e.g., from Development to Production) using the FlutterFlow environment selector.

Observe that the selected Supabase project remains the same across all environments; there is no option to bind a different project to a specific environment.

Attempting to change the project in one environment overwrites the configuration for all other environments.

Reproducible from Blank

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

Bug Report Code (Required)

IT4gi/Llz4VgocRE15SJKe9WjjsvJVgmaIc0sNobbxAjIoDoPJkUacz8alBVcOaoS3xHKEWJmnEypfONvvLlG/oEITCVRphjyZYAEjnKWlK/aovREaiOXHR6EfNhfR2A0cHYhyZAA7J2V3Bg3TuUFt6RQi7vQaX6Zwh9f6PHaOI=

Visual documentation

Environment

- FlutterFlow version: 6.6.24

Additional Information

No response

[Juansarmi]

Hi! Sorry you're running into this issue.

I completely understand your point. At the moment, the way Supabase is implemented comes with this limitation. I’ll forward your request to our engineering team as a feature request, including your suggestion about supporting different Supabase databases across different environments.

I’ll keep you posted as soon as I have any updates.

Best regards