Hi all,
I’ve been iterating pretty quickly on my UI lately, changing layouts, renaming elements, moving things between views, that kind of stuff. At first it was fine, but now I’m starting to run into weird issues where parts of the UI don’t update correctly or behave inconsistently after a few changes. Nothing outright breaks, but it feels like some state is sticking around when it shouldn’t. Restarting the app sometimes fixes it, sometimes not, which makes it even harder to pin down.
I’m not doing anything fancy, just regular bindings and some basic view switching, but I’ve definitely been moving things around a lot during testing. It’s starting to slow me down because I’m second-guessing whether a bug is in my logic or just something left over from previous changes.
Has anyone else run into this kind of ghost state while iterating? How do you usually track down what’s actually causing it?

Thanks for the report, Steve. Could you share a bit more detail about the inconsistencies you’re seeing? For example, what parts of the UI aren’t updating as expected, and under what conditions does it tend to happen?

If you’re able to provide clear reproduction steps (or even a small sample project), that would really help us investigate and narrow down whether this is an issue in the framework or something specific to your setup.

In the meantime, the Inspector tool can sometimes help track down stale or unexpected state. It’s typically only available to licensees, but in this case we may be able to grant you access so you can experiment with it and see if it sheds any light on the issue.