Can we access your project?
Current Behavior
The MODD Flutter Flow project validates successfully, but Flutter Flow’s server-side Flutter code export fails every time with:
Unexpected error from the server.
Status: 400
Body: Error generating code for the project. Make sure there are no project errors.
The failure occurs both when Flutter Flow AI attempts to refresh the generated-code snapshot after a successful project push and when export is attempted directly through the Flutter Flow CLI. The validation stage succeeds before the export attempt. The error provides no project-error identifier, affected file, or actionable diagnostic.
Expected Behavior
After successful project validation, Flutter Flow should generate/export the Flutter code successfully, or return a specific project error identifying the configuration, page, widget, action, or resource that prevents export.
Steps to Reproduce
1.Open the existing FlutterFlow project MODD (project ID: modd-cd48xq).
2.Confirm the project passes FlutterFlow validation.
3.Attempt a server-side Flutter code export.
4.The issue can be reproduced through FlutterFlow AI by running:
flutterflow ai run dsl/edit.dart --project-id modd-cd48xq --commit-message "test export"
5.The project push and validation complete successfully.
6.FlutterFlow then attempts to download/export the generated Flutter code snapshot.7.Observe the HTTP 400 error:
Error generating code for the project. Make sure there are no project errors.
This is reproducible after successful commits including eu1KAz62f8NMWRUudDFI.
Steps to Reproduce
1.Open the existing FlutterFlow project MODD (project ID: modd-cd48xq).
2.Confirm the project passes FlutterFlow validation.
3.Attempt a server-side Flutter code export.
4.The issue can be reproduced through FlutterFlow AI by running:
flutterflow ai run dsl/edit.dart --project-id modd-cd48xq --commit-message "test export"
5.The project push and validation complete successfully.
6.FlutterFlow then attempts to download/export the generated Flutter code snapshot.7.Observe the HTTP 400 error:
Error generating code for the project. Make sure there are no project errors.
This is reproducible after successful commits including eu1KAz62f8NMWRUudDFI.
Reproducible from Blank Leave unchecked. This occurs in an existing project; I have not reproduced it from a blank project.
Reproducible from Blank
Bug Report Code (Required)
6I2KBCgdhVaRKifIN1ys
Visual documentation
Environment
- FlutterFlow version: FlutterFlow AI SDK 0.0.40
- Platform: Windows desktop / FlutterFlow web project
- Browser name and version: [enter your browser/version if reproducing in web]
- Operating system and version affected: Windows [enter version]
- Project ID: modd-cd48xq
Additional Information
flutterflow ai run dsl/edit.dart --project-id modd-cd48xq --commit-message "test export" Error generating code for the project. Make sure there are no project errors.flutterflow export-code --project modd-cd48xq --dest .generated_debug_tmp --no-parent-folder --as-debug --include-export-manifestis blocks testing and release preparation because Flutter code cannot be exported despite successful project validation. The project has been repaired to use Firebase Authentication and Firestore as the authoritative backend, and conflicting Supabase Auth/Postgres assumptions were removed. Firebase/Auth changes validate successfully, but the export endpoint still returns the same generic HTTP 400 without identifying a remaining project error.
Can we access your project?
Current Behavior
The MODD Flutter Flow project validates successfully, but Flutter Flow’s server-side Flutter code export fails every time with:
Unexpected error from the server.
Status: 400
Body: Error generating code for the project. Make sure there are no project errors.
The failure occurs both when Flutter Flow AI attempts to refresh the generated-code snapshot after a successful project push and when export is attempted directly through the Flutter Flow CLI. The validation stage succeeds before the export attempt. The error provides no project-error identifier, affected file, or actionable diagnostic.
Expected Behavior
After successful project validation, Flutter Flow should generate/export the Flutter code successfully, or return a specific project error identifying the configuration, page, widget, action, or resource that prevents export.
Steps to Reproduce
1.Open the existing FlutterFlow project MODD (project ID: modd-cd48xq).
2.Confirm the project passes FlutterFlow validation.
3.Attempt a server-side Flutter code export.
4.The issue can be reproduced through FlutterFlow AI by running:
flutterflow ai run dsl/edit.dart --project-id modd-cd48xq --commit-message "test export"
5.The project push and validation complete successfully.
6.FlutterFlow then attempts to download/export the generated Flutter code snapshot.7.Observe the HTTP 400 error:
Error generating code for the project. Make sure there are no project errors.
This is reproducible after successful commits including eu1KAz62f8NMWRUudDFI.
Steps to Reproduce
1.Open the existing FlutterFlow project MODD (project ID: modd-cd48xq).
2.Confirm the project passes FlutterFlow validation.
3.Attempt a server-side Flutter code export.
4.The issue can be reproduced through FlutterFlow AI by running:
flutterflow ai run dsl/edit.dart --project-id modd-cd48xq --commit-message "test export"
5.The project push and validation complete successfully.
6.FlutterFlow then attempts to download/export the generated Flutter code snapshot.7.Observe the HTTP 400 error:
Error generating code for the project. Make sure there are no project errors.
This is reproducible after successful commits including eu1KAz62f8NMWRUudDFI.
Reproducible from Blank Leave unchecked. This occurs in an existing project; I have not reproduced it from a blank project.
Reproducible from Blank
Bug Report Code (Required)
6I2KBCgdhVaRKifIN1ys
Visual documentation
Environment
Additional Information
flutterflow ai run dsl/edit.dart --project-id modd-cd48xq --commit-message "test export" Error generating code for the project. Make sure there are no project errors.flutterflow export-code --project modd-cd48xq --dest .generated_debug_tmp --no-parent-folder --as-debug --include-export-manifestis blocks testing and release preparation because Flutter code cannot be exported despite successful project validation. The project has been repaired to use Firebase Authentication and Firestore as the authoritative backend, and conflicting Supabase Auth/Postgres assumptions were removed. Firebase/Auth changes validate successfully, but the export endpoint still returns the same generic HTTP 400 without identifying a remaining project error.