Skip to content

Test mode not displaying certain screens that do appear in the published version #6053

Open
@jackyminkler

Description

@jackyminkler

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

Random pages are not displaying at all, despite seemingly no issues, and they appear after I publish the page.

Expected Behavior

View all pages and elements within test mode.

Steps to Reproduce

  1. Have some random pages (no clue what exactly is affecting it, but it's definitely on my more complex pages. Sometimes with multi DB calls or a bunch of conditionals.)
  2. Run in test mode. - see there is no display
  3. Publish. - see there is content being displayed

Reproducible from Blank

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

Bug Report Code (Required)

there isn't one

Visual documentation

Image

Image

Environment

- FlutterFlow version: latest update (6/24/25)
- Platform: Web
- Browser name and version: chrome, Version 137.0.7151.120
- Operating system and version affected: laptop, macOS, Sequoia 15.5

Additional Information

I was getting really frustrated because I couldn't figure out what was wrong. Despite everything looking right, the test mode wasn't displaying anything. If I want to send this link out for beta testing this week, I can't make any changes to the published mode without potential disruptions. Publishing is the only way right now I can test what the real app looks like and that takes a significant time to do each change also.

I brought the code to cursor, and it said that the Test Mode uses Flutter/Dart version 1.19.1 while my app is locked in with version 1.19.0. I wasn't able to find how to auto- or manually update these since the dependency page says, "These are Dart packages that the code generated by FlutterFlow depends on. You cannot edit or remove these."

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