Screen Copy also duplicates invisible components, be aware

In my case I have a second database, of which the name is the same as the original one, but it doesn’t share the same data, so I had to manually reselect to the proper DB all the blocks, I also tried to delete the DBcopy and after reselecting the app stopped responding.

I copied a screen and when I use it I notice that it copies also the invisible components used in it, like local DB, so now I have 2 localDB1 that DON’T share the same data, so I have to manually change every block that uses localDB, rename it to be sure to use the right one, but the last time i deleted the copy one I think the app broke, so I left them both and used them both but now I have the problem that I can’t recall one or the other with the any components block.

The solution to this should be to either add the localDB to the any component blocks choices or to not copy the invisible components of the screen.

Just wanting to know if anyone had to deal with this and what do they think, if this is supposed to happen or will it be fixed

Thanks for flagging this @maxb - I’ve managed to reproduce this behaviour in this sample app:

https://x.thunkable.com/projects/5f04649638596966eea7d601/5ec60dda-79fc-479b-bf4a-323087f36aa6/designer

Have you logged this as an issue in Github? (It’s seems pretty familiar to me!)

No, I’m not familiar with Github