My browser / operating system: MacOS Macintosh X 10.10.5, Chrome 87.0.4280.88, No Flash version detected

Note: I posted this on the “problems with cloud data” thread but I'm posting it here as well because I don't know if people look there. Really sorry if this doesn't make sense…

OK, here goes… About a week ago I released a very complex cloud project. Now, just now, I went to check the “see data” thingy and it shows that people have been updating the cloud data! Hooray! Right? Wrong! Because for some reason, all the cloud variables are still empty every single time I check them, even though from “see data” they are NOT empty! This means that many hours of work have gone completely to waste because my cloud variables are not saving their values, despite the fact the “see data” menu indicates that they ARE in fact, saving their values. Now I feel bad because several scratchers think that they've done those things in the cloud, when, in reality, it hasn't worked at all! HELP! Why aren't my cloud variables updating? This must be a bug with Scratch, and not my project, because they only show their values in the See Data menu but NOT in the project!

Edit: I figured out a way to fix it but this is still a bug.

NullPointerException: myLife does not exist.

I don't totally understand what you're saying, so the bug is
"Cloud data is saving, but let's say

set [cloud variable] to [1]

when you refresh, the cloud variable isn't 1.
If that's what you're saying, I know the answer.
Possible replies:
-Internet is stubby
-You are a new scratcher
My theory:
If you did

set [kloud variable] to [...]

instead of

forever
set [kloud variable] to [...]
end

Most likely the first one won't work. Scratch cloud variables rarely saves it, but if you loop it, the chance of cloud variable written down is high. That's how a project with highscore works.

GunesKing wrote:

I don't totally understand what you're saying, so the bug is
"Cloud data is saving, but let's say

set [cloud variable] to [1]

when you refresh, the cloud variable isn't 1.
If that's what you're saying, I know the answer.
Possible replies:
-Internet is stubby
-You are a new scratcher
My theory:
If you did

set [kloud variable] to [...]

instead of

forever
set [kloud variable] to [...]
end

Most likely the first one won't work. Scratch cloud variables rarely saves it, but if you loop it, the chance of cloud variable written down is high. That's how a project with highscore works.

Thank you, but there was no looping (There was no highscore either. It's much more complex than that.) It turned out to be a bug relating to transfering a project between accounts (downloading and uploading) causing the variables not to show their actual values in the project. This was fixable by renaming the variables, weirdly enough.

NullPointerException: myLife does not exist.

Please provide a link to the project this bug occurs on. Also try renaming the Cloud variables that don't work.

Chiroyce wrote:

Please provide a link to the project this bug occurs on. Also try renaming the Cloud variables that don't work.

Did you read my last post? I did rename them, and they did work. Here's a link: https://scratch.mit.edu/projects/509578985/ And I'm pretty sure the cause of the bug was transfering the project between accounts (downloading and uploading) Still hope this gets fixed, as it took me a week before I realized there was a cloud data issue, and was likely annoying for users!

NullPointerException: myLife does not exist.

Fun_Cupcake_i81 wrote:

Did you read my last post?

Oops, sorry – my bad

Chiroyce wrote:

Fun_Cupcake_i81 wrote:

Did you read my last post?

Oops, sorry – my bad

It's OK! Anyways, this could probably be closed since I resolved it, but it's still an annoying bug that needs attention from the ST.

NullPointerException: myLife does not exist.