Supabase integration migration breaks project (auth + database unusable, cannot compile)

[gmria7436-svg]

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

After the new Supabase integration migration prompt in FlutterFlow, reconnecting Supabase breaks the project.

Steps performed:

• Open existing project using Supabase (auth + database actions)
• Click “Reconnect Supabase”
• Select the Supabase project

Result:

• Supabase tables are visible in Integrations
• Authentication shows warning: “Supabase has not been set up yet”
• All database actions fail with:
  “Must enable database in order to define database action”
• Project shows hundreds of errors and cannot compile

Important:
This happens even on:

• an older manual backup (10 days old)
• a duplicated project

So the issue is not project-specific.

Expected Behavior

After reconnecting Supabase, the project should:

• correctly recognize Supabase authentication
• keep existing database actions valid
• allow compilation without errors

Steps to Reproduce

1. Open an existing FlutterFlow project using Supabase (auth + database)
2. Go to Supabase integration
3. Accept “Our Supabase integration is changing”
4. Click “Reconnect Supabase”
5. Select the Supabase project

Result:

• Authentication becomes invalid
• Database actions break
• Project cannot compile

Reproducible from Blank

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

Bug Report Code (Required)

IT8oi87huJFOxPVd+KqJb8FVmiURNUM4RL8klcJTZA81GJToPZkqY+HBPhdWON+4YWlHGVKgnjs006HKhIbXVMEnPQqtGZQ/3JVpEAvyUkijSrqrEZDoOXJPI9JMG0C807avox1GA+F2SUFn3UOMCfK9HzPXQZDMNVYnOc+hDJrUnnCJKiW3VyMz6GoXAx7eTI5ODEz25eKMrop5yfj/0w==

Visual documentation

Attached screenshots show:

1. Supabase migration popup
2. Supabase tables visible in Integrations
3. Authentication warning: “Supabase has not been set up yet”
4. Database action errors: “Must enable database in order to define database action”
5. Reproducible on backup and duplicate projects

Environment

- FlutterFlow version: v6,6,13 realeased March 20, 2026
- Platform:Web (Chrome)
- Browser name and version:Chrome (Mac)
- Operating system and version affected: macOS

Additional Information

This issue completely blocks development:

• Cannot compile the app
• Cannot use Supabase authentication
• Cannot use database queries

The issue started after the Supabase integration migration prompt.

Screenshots attached:

• Supabase integration showing tables
• Authentication warning
• Database action error

[gmria7436-svg]

Additional details:

• This issue blocks production completely.
• The app cannot be compiled anymore.
• iOS build is also impacted (app stuck on blank screen).
• Android build was still working before migration.

This started immediately after accepting the Supabase integration migration prompt.

Important:
I did NOT change any logic, database, or authentication setup before this happened.

This strongly suggests the issue is caused by the new Supabase integration system.

Please advise on how to:

• restore previous working integration
  OR
• correctly migrate without breaking existing projects.

[gmria7436-svg]

Additional details:

• This issue blocks production completely.
• The app cannot be compiled anymore.
• iOS build is also impacted (app stuck on blank screen).
• Android build was still working before migration.

This started immediately after accepting the Supabase integration migration prompt.

Important:
I did NOT change any logic, database, or authentication setup before this happened.

This strongly suggests the issue is caused by the new Supabase integration system.

Please advise on how to:

• restore previous working integration
  OR
• correctly migrate without breaking existing projects.

[gmria7436-svg]

Additional details:

• This issue blocks production completely.
• The app cannot be compiled anymore.
• iOS build is also impacted (app stuck on blank screen).
• Android build was still working before migration.

This started immediately after accepting the Supabase integration migration prompt.

Important:
I did NOT change any logic, database, or authentication setup before this happened.

This strongly suggests the issue is caused by the new Supabase integration system.

Please advise on how to:

• restore previous working integration
  OR
• correctly migrate without breaking existing projects.

[gmria7436-svg]

Additional details:

• This issue blocks production completely.
• The app cannot be compiled anymore.
• iOS build is also impacted (app stuck on blank screen).
• Android build was still working before migration.

This started immediately after accepting the Supabase integration migration prompt.

Important:
I did NOT change any logic, database, or authentication setup before this happened.

This strongly suggests the issue is caused by the new Supabase integration system.

Please advise on how to:

• restore previous working integration
  OR
• correctly migrate without breaking existing projects.

[gmria7436-svg]

Additional details:

• This issue blocks production completely.
• The app cannot be compiled anymore.
• iOS build is also impacted (app stuck on blank screen).
• Android build was still working before migration.

This started immediately after accepting the Supabase integration migration prompt.

Important:
I did NOT change any logic, database, or authentication setup before this happened.

This strongly suggests the issue is caused by the new Supabase integration system.

Please advise on how to:

• restore previous working integration
  OR
• correctly migrate without breaking existing projects.

[gmria7436-svg]

• Additional details:

• This issue blocks production completely.

• The app cannot be compiled anymore.

• iOS build is also impacted (app stuck on blank screen).

• Android build was still working before migration.

This started immediately after accepting the Supabase integration migration prompt.

Important:
I did NOT change any logic, database, or authentication setup before this happened.

This strongly suggests the issue is caused by the new Supabase integration system.

Please advise on how to:

• restore previous working integration
  OR
• correctly migrate without breaking existing projects.

[gmria7436-svg]

Additional details:
Issue is blocking production after Supabase migration.

[gmria7436-svg]

Additional details:
Issue is blocking production after Supabase migration.

[gmria7436-svg]

Additional details:
Issue is blocking production after Supabase migration.

[gmria7436-svg]

Additional details:
Issue is blocking production after Supabase migration.

[khalimovamir]

I can confirm this issue on my side as well.

Supabase is connected successfully and the schema is imported, but FlutterFlow still shows “Supabase has not been set up yet” in Authentication.

I reproduced the same issue in a brand new empty FlutterFlow project connected to the same Supabase project, so this does not seem to be project-specific.

Additional symptoms:

• related Database Action errors appear
• the issue started after the new Supabase integration / migration flow
• another older project may still work, but new or reconnected projects show the warning

This looks like a FlutterFlow regression or a problem with the new Supabase integration/auth validation.

[leandrucarvalho]

The exact same thing happened in my project

[agreaves]

hey folks, we're aware of this issue and are rolling out a fix shortly. Apologies, and thank you for your patience.

[fmf-fmf]

Same problem in the projects here.