Generated code export consistently fails with HTTP 500 "Unknown error"

[sasowindustry-maker]

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

Generated code export consistently fails for this project with an HTTP 500 server error.

Project ID:
nondakke-memory-support-h42yd9

Project name:
Nondakke Memory Support

Current head commit:
zhuyCpwzXHvlKkya1UNg

Observed failed export timestamp:
2026-08-31T13:38:44.852997Z

Exact error:

Unexpected error from the server.
Status: 500
Body: Unknown error
Error running the application: Unexpected error from the server.

I performed a read-only diagnostic investigation using FlutterFlow CLI, FlutterFlow AI SDK, Codex, and FlutterFlow MCP.

The following has been confirmed:

• FlutterFlow MCP connection is healthy.
• Project inspection through MCP succeeds.
• Local and server head commits match.
• The project is clean (dirty=false).
• The failure occurs during the FlutterFlow CLI export-code server/download phase.
• The failure occurs before a usable generated-code snapshot or export manifest is received locally.
• Local Flutter pub get for generated code is never reached.
• Local generated-code static analysis is never reached.
• No request ID, operation ID, server stack trace, compiler diagnostic, dependency error, schema error, or Custom Code error is exposed to the client.

The project currently has three separate validation findings involving component parameters:

• KeypadButton.tapAction
• Button.fullWidth
• NavItem.target

There is also a warning for a small loading indicator.

However, no available export log or diagnostic metadata connects any of these findings to the HTTP 500 error.

No project modifications were made during this investigation.

Because the server response only contains "Unknown error", the actual cause cannot be determined from client-visible diagnostics.

Please inspect the server-side export-code logs for this project and determine the internal cause of the HTTP 500 error.

Expected Behavior

Generated code export should complete successfully and provide the generated-code snapshot and export manifest for the current project.

If the export cannot be completed because of a project-specific issue, FlutterFlow should return an actionable error identifying the affected resource or cause instead of an opaque HTTP 500 "Unknown error".

Steps to Reproduce

1. Open the FlutterFlow project:
   Project ID: nondakke-memory-support-h42yd9
   Project name: Nondakke Memory Support

2. Use the current project head:
   zhuyCpwzXHvlKkya1UNg

3. Attempt to export/download the generated Flutter code.

4. FlutterFlow begins the export process and reports:
   "Downloading code with the FlutterFlow CLI..."
   "You are exporting project nondakke-memory-support-h42yd9."

5. The export then fails with:

   Unexpected error from the server.
   Status: 500
   Body: Unknown error
   Error running the application: Unexpected error from the server.

6. No usable generated-code snapshot or export manifest is received locally.

Observed failed export timestamp:
2026-08-31T13:38:44.852997Z

The failure occurs during the FlutterFlow export-code server/download phase, before local Flutter pub get, generated-code static analysis, or local generated-code processing is reached.

The issue has been investigated with read-only diagnostics. The project remains clean, and the local and server head commits match.

Reproducible from Blank

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

Bug Report Code (Required)

IT5TismAvJR1oflC7q6JbflV/SYWH2E7auYrlexuGAEdDOvxEJoMOvfSbXFIOsukTHNYPWGi8XE1w9HGvePLEu49PiiWQKpc/qVhEgnwTmGieLKrEaqOPH9TEf1mGUOHzbSZhRJ/PtJiLWNm7UOIHum8cDHtQpz3OWw/GMmlNdvPnF6VGwzOXn0Jg1ZSfCvr

Visual documentation

Screenshot attached showing the generated-code export failure with HTTP 500 "Unknown error".

The failure occurs during the FlutterFlow export-code server/download phase before generated code is received locally.

Environment

- FlutterFlow - FlutterFlow version: Current production version as of August 31, 2026
- Platform: FlutterFlow Desktop App on macOS
- Browser name and version: N/A for the reproduced Desktop/MCP investigation
- Operating system and version affected: macOS Tahoe 26.2, Apple Silicon
- Flutter version: 3.47.2 stable
- Dart SDK version: 3.13.2 stable (macos_arm64)
- FlutterFlow CLI: 0.0.39
- FlutterFlow AI SDK: 0.0.40version: 
- Platform:
- Browser name and version:
- Operating system and version affected:

Additional Information

This issue is currently blocking development of this project.

The application itself has already progressed significantly, but I cannot continue reliable generated-code verification, static analysis, or build validation because every generated-code export attempt fails with the server-side HTTP 500 "Unknown error".

I intentionally stopped making further project changes until the cause of the export failure can be identified, to avoid introducing unrelated changes while diagnosing the issue.

The local development environment and FlutterFlow MCP connection have been independently verified and are working correctly.

If possible, please inspect the server-side export logs for the failed attempt around:

2026-08-31T13:38:44.852997Z

Project ID:
nondakke-memory-support-h42yd9

Current head:
zhuyCpwzXHvlKkya1UNg

I would especially appreciate confirmation of the internal exception or failure reason behind the HTTP 500 response, and whether any specific project-side change is required.

[Alezanello]

Hello!!

I also tried exporting the project and encountered the same error. Unfortunately, I don’t have the tools available to assist you further, as this GitHub issue tracker is intended for reproducible bugs in new, blank projects.

For further assistance with your specific project, please contact FlutterFlow Support via the in-app chat or at support@flutterflow.io. They’ll be better equipped to investigate the issue with you.

Thank you!

[vdevc]

Hello @Alezanello!

I have the same problem and already contacted support three times.
I have already tracked down the issue which stands between two snapshots that are only one minute apart. That's too short a window for a substantial manual edit, which makes me suspect this isn't a normal content change but a corrupted or partial autosave — possibly caused by a network hiccup or a save-process race condition on your end — that left the underlying project state in a way that passes your editor's own validation (the Builder shows no project errors on this snapshot) but crashes the codegen/export pipeline.

On the community forum there are also a couple of posts reporting the same issue: for example this and this.

This is an evidence that is not project specific in my opinion. Please consider we are completely stuck as either code export as well as flutterflow ai refresh-context and local run functionalities are unaccessible.

Thanks for escalating this internally!