Chrome Preview fails to compile due to generated Supabase/PostgREST compatibility error

[Busstopspassengers]

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

FlutterFlow AI test and project validation pass, but Chrome Preview fails during Flutter compilation and the app cannot launch.
A clean regeneration reproduces the same issue.
The generated generic Postgres/Supabase code references missing SupabaseStreamFilterBuilder / SupabaseStreamBuilder types and generates a PostgrestQueryBuilder call incompatible with postgrest 2.4.2.
Checks already completed:
Custom functions/actions/widgets: 0
Custom project pub dependencies: 0
No custom package is forcing an incompatible PostgREST version
Clean regeneration reproduces the failure
FlutterFlow validation passes, but interactive Chrome Preview cannot compile
I have not manually modified the generated files because they may be regenerated. Please investigate the FlutterFlow-generated Postgres/Supabase backend code compatibility.

Expected Behavior

Chrome Preview should compile and launch successfully using FlutterFlow-generated Supabase/PostgREST code after project regeneration.

Steps to Reproduce

Open the existing FlutterFlow project.
Run FlutterFlow AI test/project validation. Validation passes.
Launch Chrome Preview.
Flutter compilation fails before the application starts.
The generated generic Postgres/Supabase code reports missing SupabaseStreamFilterBuilder / SupabaseStreamBuilder types.
The generated PostgrestQueryBuilder call is incompatible with postgrest 2.4.2.
Perform a clean regeneration/build.
Launch Chrome Preview again.
The same generated-code compilation errors occur.

The project has 0 custom functions/actions/widgets and 0 custom project pub dependencies, so no custom package appears to be forcing the incompatibility.

Reproducible from Blank

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

Bug Report Code (Required)

IT4Wls/qxItPxd9G176JbvpagiovJj8hU403mMN+UQgaF4jpO7YPXfikSEpWZ9+kTHxcL1mggnE0zPCLvdnqA+UoPTKCc4A9+ZZAZRbjQk6iRbnTBqmKdEFQQOlJJVyv4J2nnBZvAMtvSEI+2WGuCty8bBbDO7q0OTIZOuaKGLP7n1WqQ0SLb3kNh1JWeC/v

Visual documentation

Chrome Preview fails during Flutter compilation before the app launches. FlutterFlow AI test and project validation pass, but interactive Preview cannot start.
The diagnostic results identify FlutterFlow-generated Supabase/PostgREST compatibility errors involving:
SupabaseStreamFilterBuilder / SupabaseStreamBuilder
PostgrestQueryBuilder incompatible with postgrest 2.4.2
A clean regeneration reproduces the same issue. There are no custom functions, custom widgets, custom actions, or custom project dependencies causing the conflict.
Screenshots are attached showing the diagnostic results and compilation issue.

Environment

- FlutterFlow version: 
- Platform:
- Browser name and version:
- Operating system and version affected:

Additional Information

No response

[Alezanello]

Hello!

Did you tried to run it directly in the console the debug run?

[Busstopspassengers]

Thanks for getting back to me.

I have tested FlutterFlow AI validation and Chrome Preview, but I have not yet run the generated project directly from the console in debug mode. I can do that next. Could you confirm whether you would like me to download/export the generated Flutter project and run flutter run locally and if so whether you want the full console output from the failed build?

The important detail is that the project is intended to be Firebase-only. A previous obsolete Postgres/Supabase configuration was removed, but the regenerated FlutterFlow code is still producing Supabase/PostgREST-related compile errors in Chrome Preview.

[Busstopspassengers]

I checked the current project configuration. There is no active Supabase, Postgres, PostgREST, relational table, dependency or API configuration in the project. The active backend is Firebase/Firestore only.

The only Supabase/Postgres references found are inside old .flutterflow/history/* snapshots from earlier project states.
The current source also contains a defensive cleanup helper that clears Postgres config if present.
So the active project appears Firebase-only, but Chrome Preview is still regenerating/failing on Supabase/PostgREST-related code.

[Busstopspassengers]

The project did historically contain Postgres/Supabase configuration, but it has been removed. The active project is Firebase-only. Historical .flutterflow/history snapshots still contain the old configuration. Could FlutterFlow's code generation be picking up stale backend metadata from the project's history or another internal project state?

[Busstopspassengers]

Hi, I tested this using FlutterFlow Desktop Local Run as requested.

I enabled the Web platform, selected Chrome as the Local Run device and ran the current project with debug logging enabled.

The project now successfully compiles and launches in Chrome locally (localhost). I did not receive the Supabase/PostgREST compilation errors during this Local Run.

The active project configuration has also been checked and is Firebase-only. There is no active Supabase/Postgres/PostgREST configuration; those references only exist in older FlutterFlow history snapshots.

So currently:

• FlutterFlow Test Mode: launches successfully
• Chrome Local Run: compiles and launches successfully
• The Supabase/PostgREST errors were occurring in the previous Chrome Preview/generated state

Please let me know if you would like any Local Run debug logs or further checks from the project.