Resetting data from .aab file

Hi, I have a problem.

My game’s load file is based on a boolean variable “Save File”. This variable changes and is saved to storage upon clearing the tutorial stage. When the variable “save file” is true, all other variables inside will then be saved to storage. Now the problem is, when I upload a new release track on google play console. My data from the previous track is loaded even though I already uninstalled the old and reinstalled the new one. My theory is that the variable “save file” is being read as true even though it should be false upon installing it for the first time.

If i clear storage in my phone settings, then the problem is gone. So I guess the problem is really on the reading of the storage

You need to start storing data in different places. For example, change the name of the storage (inside the game).

1 Like

Your theory is wrong. It saves in one place on the device. Then, when you get data, you get the saved data from the device. It can remain even after the app is deleted.

There’s no problem with your save or the game being uninstalled and reinstalle, then the data loads the old data.

Like he said when the game is deleted the data still is left there.

It’s actually a good thing, specially if you game doesn’t use any cloud saves however i see your point and what you mean.

1 Like

Okay, so I should just change the name of the storage right? Thanks. I’lll try that


additionally. HOw do I fix this issue from google play console

I can’t tell you about the error (I didn’t even try to do anything for the phones, save or anything). You’re better off asking for help from those who published the games on Google Play.

However, it seems that this is not an error, but rather a warning for certain games or applications.

1 Like

I wish i could show you a screenshot for my game, it has samething like that everytime i update it.

However do note from my experience, that warning has/had no effect on my game in way or form. I particularly suspect that, this is between the engine codes and how the google playstore sees.

I could be wrong, but i ignored that and on my every update i put out, it has been there and im guessing it will be there too in the future

1 Like

I’m guessing it’s how Gdev codes compile when it’s been converted to aab. I haven’t received any issue from it and so on

1 Like

Okayy thanks for the help guyss