Skip to content

Generated code export fails with HTTP 400 despite project passing validation #7375

Description

@MSHSportsHub

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

My FlutterFlow project is unable to generate/export Flutter code. Each attempt to generate the code fails with HTTP 400 and the message:
“Error generating code for the project. Make sure there are no project errors.”
I have already worked through the project validation issues and retried code generation multiple times. The project now passes FlutterFlow validation and SDK/preflight validation with 0 errors, but generated-code export continues to fail with the same HTTP 400.
Firebase is connected successfully, Cloud Firestore has been created, Firebase Authentication is enabled, and the Firebase configuration has been generated. Firebase Storage is intentionally not enabled at this stage.
I also corrected previously identified component parameter/preflight issues and retried code generation afterward, but the HTTP 400 remains.
The problem is that FlutterFlow validation does not identify a blocking project error, while the code-generation service still reports that project errors are preventing generation.

Expected Behavior

If the project passes validation with 0 errors, FlutterFlow should successfully generate/export the Flutter code. If a project issue is preventing code generation, FlutterFlow should identify the specific page, component, action, binding, custom function, or other project element causing the failure rather than returning a generic HTTP 400.

Steps to Reproduce

1 - Open the existing MySportsHub project in FlutterFlow.
2 - Run FlutterFlow project validation.
3 - Project validation completes with 0 errors.
4 - SDK/preflight validation also completes with 0 errors.
5 - Attempt to generate/export the Flutter code.
6 - Code generation fails with HTTP 400.
7 - The returned message is: “Error generating code for the project. Make sure there are no project errors.”
8 - Retry code generation after refreshing the project/context.
9 - The same HTTP 400 error occurs despite there being no reported validation errors.

This has been reproduced multiple times after resolving previously reported project/preflight errors.

Reproducible from Blank

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

Bug Report Code (Required)

IT40i87huIVPsbRJ0LX1bcJKmjk5JVs2RLsnjMJraCAsfZT2BLMcec/RVERVOLynSnxIOWGjnnIdwqDHkc72A+UrEy+BfrZ+zZd+TRXKUkmiSqqICpDtXUckM/NJJVyE0cOo2SNNA7Z1WiEg2zimDOTITj7cCb70DTMzMeWXJr7JjHepQ0SLb3kNh1JWeC/v

Visual documentation

Generated-code export consistently fails with HTTP 400 even though the project currently passes validation with 0 errors. Screenshots are included where available. FlutterFlow team has permission to access the project to reproduce and inspect the failure directly.

Environment

- FlutterFlow version: Current production version as of August 10, 2026
- Platform: macOS Desktop App
- Browser name and version: Google Chrome (current version), also using FlutterFlow - - macOS desktop app
- Operating system and version affected: macOS

Additional Information

This issue is currently blocking development because I cannot generate/export the Flutter code despite the project passing validation.
Troubleshooting already completed:
Firebase project is successfully connected to FlutterFlow.
Firebase configuration files have been generated.
Cloud Firestore is configured.
Firebase Authentication is configured.
Previously identified project validation/preflight errors have been corrected.
Current FlutterFlow validation reports 0 errors.
Current SDK/preflight validation reports 0 errors.
Code generation has been retried after the above corrections and continues to return HTTP 400.
Firebase Storage is intentionally not deployed yet and should not be required for Flutter code generation.
The remaining project warnings do not appear to be classified by FlutterFlow as blocking errors.
Please investigate whether there is an internal/hidden project reference or code-generation service error that is not being surfaced by FlutterFlow validation. If a specific project element is preventing generation, please identify the page, component, action, binding, custom function, or reference responsible.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions