The outcome from that post was to move the component around a slightly and that somehow resolved. it. I am able to do the same thing as a workaround but I am opening a new post because this bug does need to be resolved. The workaround can only be a temporary fix.
Additional info: (Cloud or Self-hosted, Screenshots)
Hi @Babs1! Thanks for reporting this and for linking the forum post, that’s super helpful! I tried multiple times but couldn’t reproduce the issue on my end. Could you share a Loom video showing the steps you take when it happens? Seeing it will really help me investigate what went wrong. Thank you!
Hey @Babs1, thanks for recording this, I still wasn’t able to reproduce the exact bug. If you’re able to share an export of your app, that would be super helpful for me to take a closer look!
Hey @Babs1, thanks for sharing your app export. I took a look and was able to reproduce the bug on my end in your export. A couple of quick clarifications to help me debug this further:
Did you convert this app from a single page app at any point?
Does the issue happen in any other apps, or only in this one?
Hey no worries! Great to hear it doesn’t happen in your other apps. Do you remember when you first created this app? If it was before March 2025, my guess is that it started out as a single page app and was later converted into a multi page app. This is just my assumption, not something confirmed, but we have seen a few cases where that migration caused bugs. Since March 2025, single page apps can no longer be created.
The good news is there’s a simple workaround! Just move the component slightly out of its original spot and then move it back. This should automatically remove the duplicated components from the other pages.
