"Widget's Conditional Visibility setting not reflected in generated code or Test Mode"

[tris8]

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

Hello,

Project: sideline-strength-etyl4r
Page: SessionRunner
Widget: TimerRow (a Row widget)

Issue: TimerRow's Visibility → Conditional is set to a Single Condition: isTimed (from the SessionInstances document) Equal To true. This is saved and persists correctly across reloads in the properties panel.

However:

Searching the generated code (Developer Menu → View Code) for isTimed returns exactly one match — the other Row's condition (columnSessionInstancesRecord?.isTimed == false). TimerRow's own condition never appears anywhere in the generated code.
The behavior matches: in Test Mode, TimerRow never renders regardless of the exercise shown, even on data confirmed (via Firestore console) to have isTimed: true.

Ruled out already:

Browser caching — tested with hard reload, full browser quit/relaunch, and a second browser entirely
Stale Test Mode session — confirmed compiles ARE fresh (an unrelated text change I made elsewhere on the same page showed up correctly in a new Test Mode session)
Wrong/duplicate variable binding — confirmed via code search that isTimed appears only once in the whole file
Stale/corrupted duplicated widget — deleted the original attempt entirely and rebuilt TimerRow from scratch (fresh Add Widget, not Duplicate); same result
Branch/environment mismatch — project shows single main branch, confirmed "Synced" with server

Question: Why would a widget's saved Conditional Visibility setting not appear in the generated code at all?

Expected Behavior

When a widget's Visibility → Conditional property is set and saved in the FlutterFlow builder (confirmed visible and persistent in the properties panel across reloads), that same condition should appear in the project's generated code, and the widget should show/hide accordingly in Test Mode.

Steps to Reproduce

1. Add a Row widget to a page.
2. Set its Visibility → Conditional using Conditions → Single Condition, comparing a Firestore document's Boolean field to true (Equal To).
3. Confirm/save the condition — the properties panel correctly shows the condition (e.g., isTimed == true).
4. Open Developer Menu → View Code and search the generated file for the field name (e.g., isTimed).
5. Observe that no if statement referencing this widget's condition appears anywhere in the generated code — only pre-existing conditions on other widgets using the same field are found.
6. Run Test Mode on a data record where the condition should evaluate to true.
7. Observe the widget never renders, regardless of the underlying data.
8. Confirm the compile itself is fresh, not cached (e.g., make and check an unrelated visible change elsewhere on the same page in a new Test Mode session — that change appears correctly, while the widget's Conditional Visibility still does not take effect).

Reproducible from Blank

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

Bug Report Code (Required)

IT4Ohcrl25NOseFF7q6JY8dKhjwXHG5/aJZMjuthTQs3B5PNGpgMecmnP1NvXfGrSlZceU6cp14x+OjrueL9G/koOT6aGd1cwqoNTwHdWlKmRL2TF7qgWnJ9O+ZgCHWO0KavhxBRKsxqSUI17TqIJ9ivQh/bHZzHDVQ8Sq/LZO4=

Visual documentation

Environment

- FlutterFlow version: v7.0.78
- Platform:web
- Browser name and version: Version 150.0.7871.125
- Operating system and version affected: Mac 12.2.1 (Monterey)

Additional Information

This is blocking a timed-exercise feature (a Row that should show a timer's controls only when a session step is marked "timed" in Firestore). The workaround — building the condition through the multi-condition "Conditions" builder with Apply Opposite Statement — works correctly for other widgets (Disable Options, Text conditionals) in this same project, but this specific case (a top-level widget's own Conditional Visibility, bound to a single database field) does not appear to compile at all.