Export Code, Local Run & CLI BROKEN since Flutter upgrade

[DamusAI]

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

Since Flutter 3.38.5, it can no longer export code via CLI, run locally or download code! Reliably get this error: Error running the application: ClientException: Connection closed before full header was received, uri=https://api.flutterflow.io/v2/exportCode

Expected Behavior

Should be able to export code via CLI & run project locally with no issues like before

Steps to Reproduce

Use CLI to export code or run app locally

Reproducible from Blank

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

Bug Report Code (Required)

IT4olvHq2892rsRE7ZPyccJV+CQUJWImRJ0818pBazwbfe+uB4kqevfOTERtXeaoSn9cM2f8v2oW0tr6iN/XU/AVHzeefL44zJZAERXiYH6mWq6XFJWgf3FQQOVmJ0zD4Ka73xEnNfpaSloa7GCyHunKTnftJYDICzM8D6/LZO4=

Visual documentation

The only thing that has chnaged is as per above screenshot. As I try to use the download code option, I do see this error. No idea what is the issue with this widget, though as I deleted it, tried again & got the same issue with another widget

Environment

- FlutterFlow version: 6.5.2
- Platform: MacOS Desktop
- Operating system and version affected: 26.2 (25C56)

Additional Information

Serious mission crticial breaking chnage issue!!!

[Alezanello]

Hello!!

I wasn’t able to replicate the issue. I was able to download your project’s code even though there are two errors present in it.

I also noticed that you have pinned the project to the latest stable version. Please remember that when using the CLI, you must specify the endpoint:

--endpoint https://api.flutterflow.io/v2-version/ff-api-service-v2-v6-4

[DamusAI]

Hi,

Thanks for the prompt response, key insight for the CLI endpoint, didn't know that.

1. I can't see those 2 errors? What does it mean that you can see errors that I cannot?

3. Yes, I had to pin back to 6.4, as if you try this in the latest 6.5, you will get the errors I saw

The behaviour since the update has been erratic. Since pinning back to the previous stable version of 6.4, I was able to run the code and download it successfully. Can you try downloading the code on the latest 6.5+ version to see if you can reproduce the errors I observed? Unfortunately, I am not at liberty to attempt this, as we have business-critical development to continue with. So I must work in a stable environment.

The issue we face working with previous pinned versions is that our app is complex and has multiple recursive library projects. These essentially must be set to current to have anything like a stable workflow. Therefore, pinning to a previous stable version of 6.4 is not a realistic long-term solution.

Are you able to see and identify exactly where the 6.5 issues occurred? I could then potentially debug the exact widgets and see what breaking changes have occurred.

Otherwise, I may need to permanently move out of the Flutter Flow GUI.

Look forward to your response & thanks a lot for your help.

[agreaves]

Hi @DamusAI, we're aware of these issues and are rolling back the "current" version in the meantime. You should see these issues resolve within the next hour. Apologies for the inconvenience in the meantime.