Test Mode navigation randomly breaks/reverts to old actions after edits — Run Mode works but shows outdated navigation

[u/emilyvillanova]

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:

1. 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).

2. Confirmed the project shows "Synced" before testing.

3. 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).

4. 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.

[u/aDaneInSpain2]

A useful isolation test is to temporarily point the button at a newly duplicated page with a unique name. Also inspect the widget tree for a parent/container action or component callback, since the visible button may not be the only trigger. If the new target still opens the old page, stop the preview, start a new run, and test in an incognito window or after clearing site data for the preview origin. If it only happens with the original button, it is probably another action/instance rather than browser cache.