Storage resetting every time user reinstalls or upgrades my app

Hi,

A number of my users have noticed that their settings (which I put in storage not properties) are being reset when the app gets updated. I'm releasing new versions regularly, so this is quite disruptive.

I've tested this locally and if I build my app multiple times and copy it on to the device, my logs show that when it attempts to load the stored value it gives 'null' and reverts to the defaults. This doesn't happen if I exit and restart the app, so they are definitely being persisted between app runs. The app UUID isn't changing in the manifest

Is this a known feature/issue or unexpected. Can I work around it somehow?

Thanks

0 jim_m_58 over 5 years ago

Are you using set/getProperty or Application.Storage set/getValue? Which device(s)

0 Dresbo over 5 years ago in reply to jim_m_58

I'm using Application.Storage. I can recreate on my Vivoactive 3 music.

0 Travis.ConnectIQ over 5 years ago

Dresbo said:
my logs show that when it attempts to load the stored value it gives 'null' and reverts to the defaults

Are you detecting the null and reverting everything to defaults, or is the issue that the null is returned in the first place?

0 Dresbo over 5 years ago in reply to Travis.ConnectIQ

The value is read as null.

I have dug into this a little more and suspect two separate things might be at play. I think the user who reported the issue may be mistaken about it occurring during upgrades. I found a bug in the code which will clear these values in another situation and it seems feasible to me that this is the culprit.

Separately, when I recreated the issue, I first built it in debug mode and then release mode to ensure I got a different artifact. I suspect this might cause the watch to not recognise them as the same application. Is that feasible?

It's hard to confirm it's not caused by an upgrade until I release a new version, which I will to fix this bug. When I do I'll ask the user to confirm this hasn't wiped the settings.

0 Travis.ConnectIQ over 5 years ago in reply to Dresbo

Dresbo said:
I suspect this might cause the watch to not recognise them as the same application. Is that feasible?

We identify apps in a few different ways, but this is typically done by comparing the manifest id. It shouldn't matter if you build debug and then release or vice-versa.