I have a screen on which the user defines a variable value with a slide button. Then the user taps OK to navigate away from that screen to the next in line. But, arriving at the new screen, the value set by the user is gone.
So, on the “value select screen” I put in a test label to display the value the user selected. The variable shows up correctly as expected and changes as expected according to the 4 slide switch options available. Then I put a test label on the next screen to verify that the variable was accessible across both screens. This label displayed no value at all. Just blank.
Because this has helped in the past, I went to the blocks and changed all instances of the variable name to an alternate name on the variable menu, and then back to the intended name (which was still on the menu). Now, I got a zero value showing up, rather than a blank, it was still not the value set by the user in the previous screen.
I have several other variables which successfully/reliably maintain their values between screen changes, so this has me stumped.
Can anyone suggest other debugging measures I can take?
I too experienced this anomaly on V2.05.
The issue was not consistent and appears to remedy itself on every second reload after removing app data. I have put this down to just one of the numerous issues we are having with the new revisions.
Darren, your tutorials are excellent. I’m a fan.
I have been putting in all manner of labels to monitor variables and can’t get anywhere. I was convinced it was my blocks causing the problem but I’ve been over them so many times now that I was about ready to give up my nascent Thunkable hobby. You have given me hope.
@penny@darren@firstname.lastname@example.org just letting you know that we’re taking a closer look at this. Darren has already provided a thorough report, but to help us resolve the issue as quickly as possible could you let us know:
Are you live testing or installing your projects?
Are you using Android or iOS?
Also, if you can create a really simple example project that reproduces this behaviour that would be super-helpful too!
yesterday, after being perplexed for a while I actually did create a simple two screen single variable app but could NOT reproduce the error.
after returning to my project app, the error seemed to only reappear on the first opening after clearing app data. hope that helps. With a refresh of data and opening app after initialising, all seems well.