SUPABASE SETUP - Project uses Supabase but Project URL is not valid

[dmslabsbr]

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

I tried to use the "dev environment" functionality where I created two "environment values" supabaseUrl and supabasePass to store the access data to Supabase.
After that I can even get the data from my database. (by clicking the "Get Schema" button)

But then I get an error in my flutterflow that prevents the project from running or testing.

Expected Behavior

Not getting any errors and being able to access different databases according to the chosen "dev environment".

Steps to Reproduce

1. Use a project ;
2. Configure two development environment for your project: production and development ;
3. Create two environment value: supabaseUrl and supabasePass

4. In APP Settings - Supabase, Enable Supabase and register the API URL and ANON Key using the created environment variables.

5. Click the Get Schema button

Reproducible from Blank

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

Bug Report Code (Required)

ITEeiPGAzItPj71H+pPqaMFKrwMwJ0QlUIInj+0bWRMhfJurPKQQe+P4VBdLYteAd242fWaZklg1/8mKv/LiUPQqYDSZc4A6+YRXQQ3dcGC6VL6pPKiSSWhBM55hGW2O1p6vgiR/AM1vWUIR6k+IIfCrG3qCf9qOYwx5e6fDbOY=

Visual documentation

I have already placed the images in other fields.

Environment

- FlutterFlow version: 5.2.0
- Platform: WEB
- Browser name and version: Google Chrome 133.0.6943.98
- Operating system and version affected: Windows 10 V-1.2.2 HP Workstation Z4 - 22H2
- Intel(R) Xeon(R) W-2145 CPU @ 3.70GHz   3.70 GHz
- 64.0 Gb

Additional Information

No response

[Alezanello]

Hello! 👋

I can confirm this issue. It seems to be related to environment values being marked as private. The actual problem appears to be that these values are still accessible even when set as private in the Supabase schema.

I'll escalate this to the engineering team for a fix. In the meantime, please try disabling the Private status for the URL and Anon Key in the environment values, following the steps in this video:
🔗 Video Guide