I'm on a paid plan and I've hit the render bug tracked in #7435 (and related #7443, #7449, #7479). Multiple pages show grey blocks instead of content, with Null check operator used on a null value and Uncaught TypeError: J.xx(...).yy is not a function in main.dart.js. The pages render fine in the editor — only at runtime they break.
A few things I want to flag that I hope help the team:
1; It also reproduces in a compiled release APK, not just the web Run/Test preview. Since the APK runs native Dart rather than the web JS, this points to something deeper than a web-only issue.
2; It's independently reproduced on blank projects in #7479: "Generate Dynamic Children" shows as active with Value = UNSET on all Columns/Rows and can't be removed or reset, causing grey areas in Run/Test. I ran into exactly this myself —
dynamic-children state that behaves as if it's set on widgets where it isn't, and values that can't be selected or cleared.
3; The team initially suggested this is expected behavior, or caused by Page/App State variables without default values, or null Firestore values. But multiple users confirm it happens on brand-new projects with no state, queries, or custom code at all — so that explanation doesn't seem to hold.
4; The breakage spread over time to pages that previously worked, eventually reaching the last page I could still use — so it's now blocking my core functionality.
I emailed support ([email protected]) on September 4th with my bug report code, plus a follow-up, but I've had no response in almost a week, and my plan has already renewed in the meantime.
Could anyone from the team share an update on the fix timeline for #7435? And is there a known workaround for the stuck "Generate Dynamic Children" state in the meantime? Any help would be appreciated.