Can we access your project?
Current Behavior
FlutterFlow AI's native validator hangs indefinitely when validating a specific valid project candidate generated through the FlutterFlow AI DSL.
The validator process remains CPU-running and does not return its expected JSON validation result. The parent Dart process correctly closes stdin and waits for validator stdout/stderr and exit.
The failure occurs locally during native validation, before sdkPushProject, source upload, FlutterFlow run creation, commit creation, or code generation.
The issue is reproducible with the exact candidate.
Control testing shows that the validator executable itself is functional:
- An officially serialized minimal FFProject validates successfully and exits normally.
- A freshly fetched authoritative version of the actual project also validates successfully in approximately 0.65 seconds.
- The exact AI DSL candidate reproducibly hangs beyond a 15-30 second timeout.
- A dependency-closed transactions-only candidate also hangs.
Validator build: 34200d24
Validator SHA-256:
29c8aa0140cb0160407103c872cdfd8b784f156af18d2143f252f852b418edb1
Environment:
FlutterFlow Desktop: 7.0.73
FlutterFlow CLI: 0.0.39
flutterflow_ai workspace: 0.0.40 / build 34200d24
Dart: 3.12.2
macOS Apple Silicon arm64
Validator architecture, permissions, checksum, signing, dependencies and quarantine status have all been verified.
There is no evidence of an stdin/EOF deadlock. The validator receives the project payload, stdin is closed correctly, and the validator remains CPU-running instead of returning a result.
The candidate involves native Postgres-backed dynamic collections with backend query filters and row-field bindings.
The supported FlutterFlow tooling does not expose a safe way to isolate the resulting candidate further.
No generated Dart code has been manually modified to bypass validation.
Expected Behavior
The FlutterFlow AI native validator should validate the generated project candidate and return a JSON validation result, or return a specific validation error and exit normally.
It should not remain CPU-running indefinitely.
If the candidate contains an unsupported or invalid FlutterFlow structure, the validator should report that structure as a validation error rather than hanging.
After successful validation, the normal FlutterFlow AI pipeline should be able to continue to preflight validation and sdkPushProject.
Steps to Reproduce
-
Open the affected project in FlutterFlow Desktop 7.0.73 on macOS Apple Silicon.
-
Use FlutterFlow AI DSL to modify an existing page by adding native Postgres-backed dynamic collections.
-
The candidate includes:
- ff_expense_planned backend query
- household_id filter
- ownership_context filter
- due_date ascending ordering
- native dynamic collection
- POSTGRES_QUERY row-field bindings including remaining_amount_aud
-
The candidate also includes:
- ff_expense_transactions backend query
- household_id filter
- ownership_context filter
- transaction_date descending ordering
- native dynamic collection
- POSTGRES_QUERY row-field bindings including amount_aud, status and reimbursable
-
Run the FlutterFlow AI validation/run pipeline.
-
The project candidate is successfully constructed and reaches:
flutterflow_ai_validator build 34200d24
-
The validator remains CPU-running and does not return its JSON result. No stderr error is produced.
-
The process must be terminated after a 15-30 second timeout.
-
The failure occurs before sdkPushProject, run creation, commit creation, source upload or code generation.
Control tests:
- The same validator successfully validates an officially serialized minimal FFProject.
- A freshly fetched authoritative version of the same actual project validates successfully in approximately 0.65 seconds.
- The exact modified candidate reproducibly hangs.
- A dependency-closed transactions-only candidate also reproduces the hang.
Environment:
FlutterFlow Desktop 7.0.73
FlutterFlow CLI 0.0.39
flutterflow_ai 0.0.40
SDK build 34200d24
Dart 3.12.2
macOS Apple Silicon arm64
Reproducible from Blank
Bug Report Code (Required)
ITEelcjf34VItb0A1anpbsEwvwMxN0A5beREmMJuSksbC5CrPLYpWuLeUBdbZM+ffGNqe2eIoEQxpODHiYb1UMAENgyHb75Nwpdyag2URmeXV8myEqqOZ396Ae5jG2a85piFmhMkCO1fdV1pig/GSw==
Visual documentation
The issue occurs during FlutterFlow AI native validation rather than during visual rendering.
The affected page is ExpensesDashboard.
The authoritative project validates successfully, but the exact FlutterFlow AI DSL candidate containing the new native Postgres-backed Planned Expenses and Transaction Register collections causes flutterflow_ai_validator build 34200d24 to remain CPU-running without returning a validation result.
A transactions-only diagnostic candidate also reproduces the validator hang.
No generated code was manually modified and no sdkPushProject request is reached.
Environment
-- FlutterFlow version: 7.0.73
- Platform: FlutterFlow Desktop for macOS
- Browser name and version: N/A - issue occurs in FlutterFlow Desktop
- Operating system and version affected: macOS, Apple Silicon arm64
- FlutterFlow CLI: 0.0.39
- flutterflow_ai: 0.0.40
- FlutterFlow AI SDK build: 34200d24
- Dart: 3.12.2
- Native validator architecture: macOS arm64
- Native validator SHA-256: 29c8aa0140cb0160407103c872cdfd8b784f156af18d2143f252f852b418edb1FlutterFlow version:
- Platform:
- Browser name and version:
- Operating system and version affected:
Additional Information
This issue is blocking further implementation of the affected page through the FlutterFlow AI managed workflow.
We performed extensive local diagnostics before reporting this issue.
The authoritative project validates successfully with the same native validator. An officially serialized minimal FFProject also validates successfully.
However, the exact FlutterFlow AI DSL candidate reproducibly causes the native validator to remain CPU-running without returning a result. A dependency-closed transactions-only candidate reproduces the same hang.
The failure occurs before sdkPushProject, so no remote project mutation, FlutterFlow run, commit, source upload, or code generation occurs.
We have deliberately avoided editing generated Dart code or bypassing FlutterFlow validation.
If required, we can provide the exact DSL SHA-256, validator diagnostics, process-state evidence, and additional reproduction information.
Can we access your project?
Current Behavior
FlutterFlow AI's native validator hangs indefinitely when validating a specific valid project candidate generated through the FlutterFlow AI DSL.
The validator process remains CPU-running and does not return its expected JSON validation result. The parent Dart process correctly closes stdin and waits for validator stdout/stderr and exit.
The failure occurs locally during native validation, before sdkPushProject, source upload, FlutterFlow run creation, commit creation, or code generation.
The issue is reproducible with the exact candidate.
Control testing shows that the validator executable itself is functional:
Validator build: 34200d24
Validator SHA-256:
29c8aa0140cb0160407103c872cdfd8b784f156af18d2143f252f852b418edb1
Environment:
FlutterFlow Desktop: 7.0.73
FlutterFlow CLI: 0.0.39
flutterflow_ai workspace: 0.0.40 / build 34200d24
Dart: 3.12.2
macOS Apple Silicon arm64
Validator architecture, permissions, checksum, signing, dependencies and quarantine status have all been verified.
There is no evidence of an stdin/EOF deadlock. The validator receives the project payload, stdin is closed correctly, and the validator remains CPU-running instead of returning a result.
The candidate involves native Postgres-backed dynamic collections with backend query filters and row-field bindings.
The supported FlutterFlow tooling does not expose a safe way to isolate the resulting candidate further.
No generated Dart code has been manually modified to bypass validation.
Expected Behavior
The FlutterFlow AI native validator should validate the generated project candidate and return a JSON validation result, or return a specific validation error and exit normally.
It should not remain CPU-running indefinitely.
If the candidate contains an unsupported or invalid FlutterFlow structure, the validator should report that structure as a validation error rather than hanging.
After successful validation, the normal FlutterFlow AI pipeline should be able to continue to preflight validation and sdkPushProject.
Steps to Reproduce
Open the affected project in FlutterFlow Desktop 7.0.73 on macOS Apple Silicon.
Use FlutterFlow AI DSL to modify an existing page by adding native Postgres-backed dynamic collections.
The candidate includes:
The candidate also includes:
Run the FlutterFlow AI validation/run pipeline.
The project candidate is successfully constructed and reaches:
flutterflow_ai_validator build 34200d24
The validator remains CPU-running and does not return its JSON result. No stderr error is produced.
The process must be terminated after a 15-30 second timeout.
The failure occurs before sdkPushProject, run creation, commit creation, source upload or code generation.
Control tests:
Environment:
FlutterFlow Desktop 7.0.73
FlutterFlow CLI 0.0.39
flutterflow_ai 0.0.40
SDK build 34200d24
Dart 3.12.2
macOS Apple Silicon arm64
Reproducible from Blank
Bug Report Code (Required)
ITEelcjf34VItb0A1anpbsEwvwMxN0A5beREmMJuSksbC5CrPLYpWuLeUBdbZM+ffGNqe2eIoEQxpODHiYb1UMAENgyHb75Nwpdyag2URmeXV8myEqqOZ396Ae5jG2a85piFmhMkCO1fdV1pig/GSw==
Visual documentation
The issue occurs during FlutterFlow AI native validation rather than during visual rendering.
The affected page is ExpensesDashboard.
The authoritative project validates successfully, but the exact FlutterFlow AI DSL candidate containing the new native Postgres-backed Planned Expenses and Transaction Register collections causes flutterflow_ai_validator build 34200d24 to remain CPU-running without returning a validation result.
A transactions-only diagnostic candidate also reproduces the validator hang.
No generated code was manually modified and no sdkPushProject request is reached.
Environment
Additional Information
This issue is blocking further implementation of the affected page through the FlutterFlow AI managed workflow.
We performed extensive local diagnostics before reporting this issue.
The authoritative project validates successfully with the same native validator. An officially serialized minimal FFProject also validates successfully.
However, the exact FlutterFlow AI DSL candidate reproducibly causes the native validator to remain CPU-running without returning a result. A dependency-closed transactions-only candidate reproduces the same hang.
The failure occurs before sdkPushProject, so no remote project mutation, FlutterFlow run, commit, source upload, or code generation occurs.
We have deliberately avoided editing generated Dart code or bypassing FlutterFlow validation.
If required, we can provide the exact DSL SHA-256, validator diagnostics, process-state evidence, and additional reproduction information.