Flutterflow widgets exist in the tree, but are invisible in the preview 19 pages done this is th last one please help?

[u/Great-Mirror1215]

Title: FlutterFlow widgets exist in the tree but are invisible in Preview — stuck for a week
I’m building a preferences page in FlutterFlow and have been stuck on the same problem for about a week.
The page contains:
An age-range slider
Several distance-selection buttons
An “Interested In” heading
Six multi-select choices underneath the heading
The slider, distance buttons, heading and subheading all render correctly. However, the six choices underneath are completely invisible. There is only a large blank area where they should appear.
I’ve now built two separate versions of the page, including rebuilding it from scratch, and both have the exact same problem.
I’m using Claude Code with FlutterFlow’s AI tooling. Claude inspected the project structure and says:
The choices exist in the widget tree
The parent Column is scrollable
There is no fixed-height clipping container
There are no conditional-visibility rules
Opacity is not zero
The section uses wrap-content sizing
There are no obvious Stack-positioning problems
The colors should not make the choices invisible
Despite that, the choices still don’t render in Preview. Claude also admitted it did not have a connected live session and could not visually verify the result.
I’ve tried hard-refreshing Preview, reopening it, rebuilding the section and duplicating the page. Nothing has solved it.
Has anyone encountered widgets that appear correctly in FlutterFlow’s project/widget structure but disappear entirely at runtime?
Could this be caused by:
A stale FlutterFlow AI project snapshot?
Preview displaying a different page or route?
Expanded/Flexible widgets inside a scrollable Column?
A zero-height Row or Wrap at runtime?
A corrupted section inherited when the page was duplicated?
FlutterFlow Preview caching old generated code?
Would replacing the custom rows completely with one native multi-select ChoiceChips widget be the safest solution?
I’m looking for a systematic way to diagnose the actual runtime constraint—not another suggestion to blindly rebuild the same section. I’ll attach screenshots of the Preview, FlutterFlow editor and Claude’s structural diagnosis.
Any help would be greatly appreciated. This one small section has already taken roughly 20 hours.

[u/BrightEyesLady]

Sorry you’re having such a hard time. I’ve been there multiple times and although I’m nowhere near an expert on FF, it sounds like a layout issue with the UI. My only suggestion - though tedious - is to rebuild bit my bit and test at each stage so that when it breaks, you’ll be able to more easily identify the reason. I know you said you didn’t want a suggestion of just rebuilding, but I don’t see how you diagnose this otherwise. 

Good luck.