again… How do you guys debug your apps?
@Tatiang, your way is awesome. I have used it some times now, and also simply displayed my different steps in labels just to make sure averything I expect to be in my variables etc actually are there.
I am trying to build carefully, step by step, view the results in labels as I said, but then the app is crashing, and that’s fine, its my bad coding. So I step back to how it was before I added this code block that Made it crash, but it still crashes, then I go back even further, but it still crashes…
And quite often I simply run-force quit-run-force quit a couple of times and then it works again, without having done anything in the code. I am guessing that if I have run the app earlier the code should be ok? So, when it crashes it’s caused by something I recently added in the code…?
So, by go back the app Should be working again, as it previously did, right?
Is this a common behaviour for Thunkable? Is this something you experienced guys are meeting sometimes as well? If so, how do you do to come back and keep coding?
Tatiangs recommandation is great, but it requires that the app is starting
I am running:
Mac OS Mojave (and sometime Catalina)
Safari 12.1.2 (at least for Mojave, I am not sure which version on Catalina right now)
Thunkable test app 267-2
I often clear cache for Safari on my Mac.
quite often I force quit the app on my phone as well.
Sometimes it works, sometimes not…