Unable to test, export code, or download project

[kcarreira]

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

Test Mode: Fails to compile with generic error message
Code Export: Shows "Failed to export code. Unexpected error from the server"
Download: Not possible due to compilation failure
Project Issues: Shows no errors

Expected Behavior

App should compile successfully for testing
Code export should work normally
Project should be downloadable
If there are errors, they should be clearly displayed in Project Issues

Steps to Reproduce

Yesterday: Project was working perfectly - could test, export, and download
Today: Suddenly stopped working with no changes made to the project
Other projects: Tested with a different app - it works fine, confirming issue is project-specific

Reproducible from Blank

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

Bug Report Code (Required)

IT4Oz/Hqx892pbxa7arAdcFvnjgWHGY5RLxMi8JhUUocF5fNG4gIZfTBXE9uOP25dgl5eWGGpGI009GNm9z1O/pcEzidbLl8+s9MFDrdcDmgV5SUDM3tRXNUGshRCX6l0bWjniNCOvpiSHAE3GCyOdyQf3XZN5jqO0cvJc6KNpPXrgfuQ0SLb3kNh1JWeC/v

Visual documentation

Environment

- FlutterFlow version: 6.1.13+
- Platform: Web and Windows Desktop
- Browser name and version: Chrome 138.0.7204.169
- Operating system and version affected: Windows

Additional Information

The error message is very generic and provides no actionable information to debug the issue. Since the project worked yesterday and no changes were made, this suggests a platform-level issue rather than a project configuration problem.

[kcarreira]

BREAKING CHANGE CONFIRMED - PLATFORM BUG

PROJECT DETAILS:

• Working perfectly until July 24, 2025
• Months of development without issues
• Preview works fine, build/export fails
• Error messages keep changing and are inconsistent:
  • Initially: Generic "Failed to export code"
  • In duplicated project: Found issue was in data schema
  • After removing all data schema: Now falsely blames custom widgets and custom actions

TESTING PERFORMED:

• Duplicated project to isolate issue
• Systematically deleted components until found data schema was causing problems
• Removed all problematic data schema from main project
• Build now fails with different error targeting custom widgets/actions
• Error messages are inconsistent and appear to be false positives

This is clearly a platform-side breaking change introduced in recent days.
The build system appears to be generating false error reports.

PROJECT IMPACT: Unable to deploy/test - blocking production release.

[Alezanello]

Hi there!

For this type of issue, please reach out to our support team via the in-app chat or by emailing support@flutterflow.io. We’re limited in what we can assist with through the GitHub Issue Tracker, as it’s primarily intended for reporting reproducible bugs that occur in new, blank projects.

Thanks for your understanding!

[Remkin1976]

Cmon alenz what about the myriad of failings in the debug panel not working altogether. Your limited in support resource. If you don't get into these issues it will be the end of flutterflow

[Alezanello]

Hello again!

Just to clarify, I’m not directing you to support arbitrarily — it’s simply that the GitHub issue tracker isn’t equipped to handle project-specific issues. This space is intended for reproducible bugs that occur in a new blank project.

As you mentioned, this seems to be tied to your specific project setup, so the best way to get the right assistance is through our support team. They have the tools and context needed to help you out effectively. You can reach them via the in-app chat or by emailing support@flutterflow.io, as noted in the previous comment.

For more details on what this GitHub repo is intended for, feel free to check the README: https://github.com/FlutterFlow/flutterflow-issues

Thanks for your understanding!

[Alezanello]

Closing this issue since we haven't heard back from you. If you are still facing the problem please submit a new issue. Thank you!