Screen deletions and merges do not persist across exports, project state inconsistent between sessions

Stitch
1

I’ve been building a fairly large multi screen app in Stitch (LocalLegacy Canada Dashboard, around 90-100 screens) and I’ve run into something pretty frustrating with how changes are (or aren’t) actually saving.

A few times now I’ve asked the AI assistant to remove specific screens or merge duplicates, and each time it tells me the change is done. But when I export the project right after, the screens are still there like nothing happened.

Some concrete examples:

- I asked for 4 screens (a “National Expansion” flow) to be removed. This got confirmed as done four separate times across different sessions, and all 4 screens came back in every export anyway, including the most recent one.

- I asked for 2 duplicate billing screens to be merged into 1. Confirmed done, but I kept getting 2-3 separate billing screens in the exports.

- I had about 8-9 screens that accidentally got duplicated (“_1” / “_2” versions of the same screen). Asked for these to be cleaned up, got confirmation, they came back later anyway.

- My total screen count has bounced around in a way that doesn’t make sense 99, then 108, then 93, then 108 again, then 100 across exports where I hadn’t made any new changes in between.

- At one point I just asked it to list out the current screens (no edits, just show me what’s there), and it gave me a list that matched an old version of the project from way before any of this cleanup started.

It feels like exports (and maybe the live project itself) are sometimes pulling from an older snapshot instead of the actual current state. It’s made it hard to trust anything the AI tells me is “done,” since it often just doesn’t match reality.

Has anyone else run into this? Is there any kind of version history in Stitch I could use to find and restore a clean version of my project?

2

Hey @Eric_Bazuaye, I completely understand the issue, and this is actually something our engineering team is actively working on. I have raised a fresh internal ticket to investigate this further. Thank you for this detailed breakdown—this is exactly the kind of insight we value from our power users!

In the meantime, I would like you to try duplicating your project to see if the deleted designs are still included in the export. Please follow these steps:

  1. Go back to your main Stitch dashboard.

  2. Click the options icon on the LocalLegacy Canada Dashboard card and select Duplicate Project.

This forces the cloud server to compile a brand-new, clean file from scratch, which strips out all hidden cache bloat, old snapshot ghosts, and messy version loops. Once you open that new copy, your screen counts should stop bouncing around!