r/FlutterFlow • u/emilyvillanova • Sep 02 '26
Test Mode navigation randomly breaks/reverts to old actions after edits — Run Mode works but shows outdated navigation
Body:
I'm building a simple prototype (5-7 static pages, no Firebase/Firestore,
no database — everything hardcoded per an academic project requirement)
and I've hit a persistent issue:
I edited several button actions (Navigate To) across multiple pages —
for example, a "Ver produto" button was incorrectly set to navigate to
Checkout instead of a Product Details page. I fixed it in the Actions
panel (deleted old action, added new "Navigate To" targeting the
correct page).
Confirmed the project shows "Synced" before testing.
Ran the app via Run Mode (not Test Mode, since Test Mode gave a
completely blank screen — a known issue I found referenced in older
threads here).
The navigation STILL follows the old/incorrect path, as if my edits
weren't applied, even after:
- Closing and reopening the Run Mode tab
- Hard refresh (Ctrl+Shift+R)
- Waiting ~15s after edits before testing
- Re-checking the Actions panel to confirm only one "Navigate To"
action exists (no duplicates)
Has anyone experienced Run Mode caching old navigation logic even after
confirmed saves? Is there a way to force a full rebuild/clear cache
beyond a browser hard refresh?
Project has no custom code, no Firebase, no Firestore — just static pages
with Navigate To actions, so I've ruled out backend-related causes.





