What kind of device are you using?: (Also include iOS version, and Hopscotch version) M1 iPad Pro (5th Gen), iPadOS 15.4, HS 3.50.2
1 sentence description of the problem (I was doing _________, and then __________ happened): I was deleting an old variable after replacing a set block with a new one, and the new one just disappeared
Steps that the Hopscotch team can take to reproduce my problem every time:
Create a variable
Place it in a set block
Create a new variable
Replace the old with the new
Delete the old variable
Become confused as the new variable disappears after tapping out of the block, even though that variable still exists
…
I expected this to happen: The new variable to remain
But instead this happened: It disappeared for no reason
Here’s a sweet screenshot: I don’t have access to hopscotch from here, sorry. I’ll add a screenshot once I’m able.
It may seem like it’s not a big deal, but it can potentially break very large projects. Affects all variable types (Local, Object, Game, and User)
So if you delete an unused variable, and the project stops working for no reason, then some set variable declarations may have been cleared/removed unintentionally.
I had this bug a few times before, and I ended up scrolling through my codes and replacing all the vanished variables for a long time. I never remembered to report this bug after spending a long time replacing the variables.
Yeah, that happens with the object variables, other variables will look like nothing happened, then vanish after tapping again. I haven’t tested if they mysteriously vanish after tapping on the variable again. This mainly only happens if you delete a variable that is currently in the set block.
Why? Is there another topic that describes this bug?
I also had no idea most (if not, all) moderators and admins would already be watching the topic.
Ok. I know it doesn’t make any difference, now, but I just turned off the tags.
thanks! will look into scheduling this. It’s not fixed yet because it’s a bit low in priority compared to some of our other bugs, but we’re working on undo/redo for variables next so this should be fixed (can’t guarantee)