I am wondering if there is a bug here that when you set/save a whole bunch of stored values before navigating to the next screen. When I first put the blocks in, it seems to work then after a while it stops. It just does not navigate to the intended screen.
The problem with this not working, is that the user then has to save the page variables first, then press another button to exit. I would have thought that this should work. Well it does sometimes.
When you call a function, Thunkable does not pause the rest of the code.
So if you stack function calls and then have a navigate block below them, the navigate command will likely happen before those functions complete. That’s especially true if you are using stored variables which are very slow.
I have setup a real simple test app, now when you first run this it works fine, but go back and forth a few times then it stops going back to the first page
We’re happy to help investigate this issue more, @thorntonp72l3. Thanks for raising it. Can you confirm all of these functions are completing upon the click event? An easy way to debug this would be to add a label after each function to show the previous function has completed. Thank you!
So I know what the problem is, which is okay I guess but I still feel this is a bug.
If you set the Stored variable with a entry from a blank input field it then stops working and you cannot even recover it as in force the stored variable to contain something. I have to actually change the variable to something else hence I now have 13 on the end of my variables.
