What kind of device are you using?: I-Pad Pro (9.7-inch)
1 sentence description of the problem (I was doing _________, and then __________ happened): I was coding my coded story chapter 1, I hit play and poof. No more project
Steps that the Hopscotch team can take to reproduce my problem every time:
Idk
Idk
….
I expected this to happen:
It let me test my project But instead this happened:
I got a blank screen Here’s a sweet screenshot:
If the code is still there, updating the project should not make you lose the code – that is a player crash that should be fixed, but it should not affect the editor or what the app transfers to the server
I had my dad play an update before I published it, he repeatedly spammed the restart button, then it broke and I had to spend another hour fixing it lol.
Nope, just a bug that’s been around for a long time. “Project crashing”. The data is saved but, within the current instance of the player, it is unable to run the code and show objects.
If the project is published, for it to save, either save it to your drafts or publish an update/remix. Then you just have to reopen the project, and it should work.
This has happened to me a few times. Just exit the project then re-enter it and everything should be back to normal. If it isn’t, then try restarting your iPad.
Ive been having this problem with a draft Ive been working on where I’ll be testing the game and after just a certain amount of time the project(not the app) will crash and will turn the screen white. I thought it was just a happen once issue and got out of the project and went back in and it started working but then after that time again it will do the same thing. If I go back to editing and start the project it will stay on the white screen until i completely exit the project. Has anyone else had this happen? Or maybe this had to do with the number of clones I created, or the z index I was setting was too high?
Looks like the bug you’re experiencing, however has been reported several times in the past (happens in drafts and published projects). I think it’s because too much device memory is being used, but I don’t know of a way to fix it other than reopening the app.