This continues happening to me, this deserves a revive.
Yeah it happened to me today
I wonder if we could instead be able to close it by shaking the device.
I can’t consistently reproduce this but it happens on a regular basis
Far more often now with the new update
This happens to me as well… every single time when adding code to an object on a different scene (perhaps it happened after adding two rules to the object). Can be resolved temporarily by quitting the app. Hope THT fixes this issue.
Possibly. Haven’t coded in a while so idrk?
this wasn’t quite resolved as it happened again yesterday but its really infrequent for me
Use this template to make awesome bug reports:
Your username: The Wild Fox
What kind of device are you using?: IPhone 12 Pro Max
1 sentence description of the problem (I was doing _________, and then __________ happened):
I was playing around with the beta editor and then when I tried to exit my project, the editing option still popped up.
Steps that the Hopscotch team can take to reproduce my problem every time:
- Use the beta editor
- Click add code
- Exit out of your project.
- See the bug
I expected this to happen:
The block editor to go away when I exit out of my project.
But instead this happened:
It did not go away.
Here’s a sweet screenshot:
I have this when i got the beta editor
Im curious, what happens when you press the code blocks?
Really, ive seen this before
Hmm good question. I’ve never tried that. Haven’t coded recently so I havem’t had the bug since I made this report actually.
I ran into this last week again
I still see this bug too!
Yeah, it is still around. It has occurred to me recently as well. However, I feel like this error generates less frequency than it has in the past, but it is not entirely gone.
Yeah me to lol
Weird bug btw
Happens to me
I’ve run into this 3 times in the past 2 day
The actually just happened to me Weird thingy idk what to call it
We are aware of this happening occasionally, but since it is not reproducible, it’s going to take some time until this bug is fixed. The workaround, for now, is restarting the app, which usually resolves the issue.