Skip to content

Generated ChapterList FlutterFlowSafeArea passes unsupported left parameter #7414

Description

@mcmsp08-ui

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

A completely fresh Chrome session reproduces the same FlutterFlow generator failure. A new Run build fails during dart2js/Web compilation at:

lib/pages/chapter_list/chapter_list_widget.dart:124:15
Error: No named parameter with the name 'left'.

The generated ChapterList calls:

FlutterFlowSafeArea(
  left: true,
  ...
)

while lib/flutter_flow/flutter_flow_util.dart:402:9 defines FlutterFlowSafeArea without a left named parameter.

Expected Behavior

FlutterFlow should generate ChapterList code that matches the current FlutterFlowSafeArea constructor signature, allowing Test/Run web builds to compile without manual edits to generated Dart.

Steps to Reproduce

  1. Close all existing FlutterFlow Test/Run tabs.
  2. Start a completely fresh Chrome session.
  3. Open the NJROTC Academy project and wait for the editor to show Synced.
  4. Open ChapterList.
  5. Start a fresh Run build.
  6. Observe “Compilation Error in ChapterList”.
  7. Expand the error output. It reports:
    • lib/pages/chapter_list/chapter_list_widget.dart:124:15
    • No named parameter with the name 'left'
    • generated left: true
    • candidate constructor at lib/flutter_flow/flutter_flow_util.dart:402:9

The same mismatch was reproduced previously from fresh editor synchronization and generated code inspection. No generated Dart, packages, dependencies, ChapterList layout, or Safe Area settings were modified.

Reproducible from Blank

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

Bug Report Code (Required)

Unavailable: Generate Bug Report Code now returns “Project Access Restricted” for this signed-in session. The attached fresh-run screenshot identifies the affected generated widget and constructor lines.

Visual documentation

The complete fresh-run error is transcribed above. A screenshot was captured, but this controlled Chrome session would not permit the file upload.

Environment

- FlutterFlow version: Current web editor build (2026-08-21)
- Platform: FlutterFlow Web editor / Web Run
- Browser name and version: Google Chrome (fresh session)
- Operating system and version affected: Windows

Additional Information

This blocks all current Test/Run verification, including validation of corrected dynamic chapter-to-quiz routing. The prior FlutterFlow in-app support conversation was titled “SafeArea signature mismatch” and is now closed. This report adds the fresh-Chrome reproduction requested for that case. No manual generated-code workaround has been applied.

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: needs triageA potential issue that has not been confirmed as a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions