deleteProperty not working on a Vivoactive?

I'm wondering if anybody else is seeing strange behavior with `Toybox.Application.deleteProperty()` on the Vivoactive.

The call to `deleteProperty` appears to work temporarily in that a `getProperty` immediately afterwards returns `null` as expected.

However, if the app is a widget and I swipe away and swipe back, then the key mysteriously returns, almost as if the change wasn't truly 'committed'.

My work around for this has been to use `setProperty` to set the value to the empty-string, and this does pass the swipe-away/swipe-back test.

This is fine temporarily I think, but I'm worried about leaking keys long-term and eventually running out of space.

Anyone else see this type of behavior?

rconradharris over 10 years ago

A little more info:

`clearProperties` works as expected.

`deleteProperty` also works if `saveProperties` is called afterwards.

I thought I remember seeing that `saveProperties` should be unnecessary now, though. It doesn't appear to be necessary for `setProperty` at least.

rconradharris over 10 years ago

Final update here:

Looks like the issue was not calling `saveProperties`.

Turns out `setProperty` and `clearProperties` needed the save call as well.

travis.vitek over 10 years ago

The ConnectIQ guys have said that you should not need to call saveProperties() or loadProperties().

Travis

rconradharris over 10 years ago

Travis:

Yeah, that's why I was so confused.

However, after testing it out quite a few times, I'm fairly convinced that it is necessary.

If I remove those the saves, I definitely see keys return after deletion--especially around widget time-outs. Wonder if there's a nasty race here.

travis.vitek over 10 years ago

Yeah. I'm sure you're right and you do currently need to call them. I was just saying that it was said that you shouldn't need to call them, and if you do I think it should be considered a bug (ConnectIQ or firmware).

Travis

Kyle.ConnectIQ over 10 years ago

I think these issues have been fixed but not released. I'll double check and let you know the status.

Kyle.ConnectIQ over 10 years ago

Having to call saveProperties() after calling deleteProperty() has been fixed and is in the 1.1.1 SDK. If this isn't the case let us know. There is another issue where saveProperties() is called before calling onStop(), so any changes you make to the object store in onStop() are lost unless you call saveProperties() yourself. This has been fixed and will be in the next release.