Stored and Cloud Variables are not working

My Stored and Cloud Variables are not working at all. neither on live testing or after installing .apk on my android device.

What to do?

1 Like

It honestly is best not to use those at the moment as they seem to be bugged. By that I mean that they seem to be causing MASSIVE lag within apps using initialized variables. I would recommend just using the local storage and Realtime DB blocks instead.

1 Like

It works for me. Would you share your blocks as a screen shot, please?

1 Like

i cannot because all the app is cloud and stored variables, but i’m sure they have problem because one time they worked and after that they did not. Note: after they worked i did not make changes but after that they did work

yes unfortunately, but this will increase the number of blocks

You say that these variables do not work. That is, after writing these variables, they return null?

In these variables, you save a list, objects or values ​​of simple types - number, string, boolean?

They are buggy, or at least when I use the bottom tab navigator, so e of them star to show null values :frowning: I love Thunkable X, but I am finding so many bugs, that sometimes is difficult to work with it


They always return to null when leave the application :disappointed_relieved::disappointed_relieved:

Hello to all.

Global variables work really strange in some cases, but to understand the situation need to see the blocks you use. Perhaps you do not initialize lists in such variables and they really will not be saved - which works correctly.

Cloud variables do not guarantee data retention for those who do not understand. Where is the data stored in Cloud variables? On web-server. If there are problems with the server or some kind of failure occurs, hackers, tricks attacked, the database administrator drank beer and did something wrong in the server configuration, then the data, of course, will not be saved.

But the Stored variables, correctly initialized, should work like clockwork and even better. Data loss on Store variables is not allowed.

1 Like

Just to be clear, cloud variables are stored on a Firebase Realtime DB, just like our Realtime DB component. Certainly, Firebase could be down, but that would be a pretty serious Google outage. The user’s device could also be offline or out of internet range.


1 Like

Yes, @abedo, please post a copy/share link to your project (see here for how) so that we can better help you.


Unfortunately, in our country there was such a situation with Google.

What if I quit the app then label 2 return to 0

  1. How do you initialize the variable “stored coies”?
  2. When you click on the button, what is in Label2.text?
  3. What if I quit the app then label 2 return to 0

Are you sure that in another place the value of “stored coies” does not change to 0? If the stored variable does not exist, then “null” will be returned. It returns 0 for you, which means that the variable exists and its value is somewhere set to 0.

I’m making a mobfight app
When button click,set Row 4 width -1 until Row 4 width = 0 (mob died)
If mob died and random a mob,earn 1 coin
If button click,set stored coins from clicking.
I remember that I can do this without Local Storage or other database to do it before.

I know my explain isn’t clearly,would you mind I send you the app copy :thinking::thinking:

You can send me a project for viewing in a personal message.

I looked at the project. On my Android, your “store” block works, saves and loads the value when you open the project. Error in your algorithm. Try step-by-step debugging to find out why Label2 is not initialized correctly when saved.

1 Like

Hy everybody,

I reactive this post because I havn’t seen it solved and I have the same issue:
=> stored variable are usable in my project neither in live test nor in apk.

I try to just save from a previous session a list:

I propably made something wrong but I didn’t fund it after many trials.

Thanks per advance for your help


when Screen1 starts, add these blocks

if stored save_favoris_list = null
set stored save_favoirs_list = empty list

also, when you set app index = “”,
change this to be = 0

This is better practice, you should declare your variable the same type you want to use it as. So if you want index to be a number, initialize as a number or nothing at all. If you want index to be text, initialize a blank text or nothing at all.

try not to initialize as a number, and then switch to text later on.