Epix FW 2.30 Property Issues

I'm getting reports that Note2Watch pairing is broken in the 2.30 firmware release for the Epix. It worked in previous versions, so appears to be a regression.

The bug appears to be related to `setProperty`; when the app uses `setProperty` to write out a value and then subsequently calls `getProperty` to read it back, instead of getting the value back like it did in 2.20, it's now getting `null`.

I don't have an Epix myself, and neither the simulator nor the Vivoactive (FW 2.90) have this issue, so I've been unable to replicate it locally.

I'm wondering if anyone else has run into a similar issue yet with their app. I'm also wondering if the new SDK will somehow magically fix this.

Aside: If you have an Epix and want to help troubleshoot this, I'd be happy to provide a debug build of the app with logging enabled so we can hone in on the issue. If you're interested, just reply here or hit me up at [email][email protected][/email].

jim_m_58 over 10 years ago

I'm getting reports that Note2Watch pairing is broken in the 2.30 firmware release for the Epix. It worked in previous versions, so appears to be a regression.

The bug appears to be related to `setProperty`; when the app uses `setProperty` to write out a value and then subsequently calls `getProperty` to read it back, instead of getting the value back like it did in 2.20, it's now getting `null`.

I don't have an Epix myself, and neither the simulator nor the Vivoactive (FW 2.90) have this issue, so I've been unable to replicate it locally.

I'm wondering if anyone else has run into a similar issue yet with their app. I'm also wondering if the new SDK will somehow magically fix this.

Aside: If you have an Epix and want to help troubleshoot this, I'd be happy to provide a debug build of the app with logging enabled so we can hone in on the issue. If you're interested, just reply here or hit me up at [email][email protected][/email].

Many of the SDK 1.1.2 changes won't work on a real device until the 1.1.2 CIQ VM is part of the firmware for the device. Under "settings>system>about" on the epix does it show the version of the CIQ VM? (it does on the va, and it's 1.1.1). If it's 1.1.2 on the Epix, note that a bunch has changed in the whole OS area since 1.1.1, and this could be the problem....

rconradharris over 10 years ago

Just an update in case anyone else runs into this problem:

I don't have access to Epix, so this is just a guess, but having seen many other 'property' bugs, I'm guessing this is an eventual-consistency issue where things are not being asynchronously written back correctly, so subsequent reads don't find the newly written key.

I think the approach I'm going to use to solve this is going to be write a `PropertyStore` class that caches values in memory and only writes them back to disk on exit.

I'm thinking of this as sort of mini Linux page-cache where values are lazily read from disk on access, and a `sync` is called only when necessary (in this case on exit, but maybe later within a timer).

No idea if this will actually fix the issue, but here's hoping...

rconradharris over 10 years ago

Another update:

Looks like the in-memory cache has helped the pairing issue but not totally fixed it.

I suspect it works when it can read from memory, but the second it falls back to the property store, it fails again.

My question is: Is the Property Store on the Epix Firmware 2.30 working at all?!

The only thing I can think to try next is maybe inserting `saveProperty` calls all over the place :(

If anyone knows what's up with the property store on an Epix, especially someone from Garmin, I'd be greatly appreciative. Thanks!

mikkosh over 10 years ago

I've noticed identical behavior. After upgrading the firmware on my Epix to fw 2.3 my app's (built with 1.1.2) property storage just ceased working. Everything (obviously) still works in the sim. So far I've not managed to find any workaround for the issue (added calls to saveProperty and even refactored the whole state saving to save a bunch of separate values instead of an array). Any help will be highly appreciated :)

Kyle.ConnectIQ over 10 years ago

We've identified an issue with the object store and devices will be rolling out an update to fix it. I don't have an exact timeline on the release for each device yet.

rconradharris over 10 years ago

We've identified an issue with the object store and devices will be rolling out an update to fix it. I don't have an exact timeline on the release for each device yet.

Thanks for the update here. Given how critical the property store is to apps across the connectIQ platform, I really hope this fix is expedited.

rconradharris over 10 years ago

I just wanted to thank Garmin for getting that Epix property issue fixed so quickly. Great stuff. *Highfive*

Brandon.ConnectIQ over 10 years ago

We aim to please. :) We often get fixes done pretty fast, but it can take time for them to make it into a release and then percolate out to our devices. In this case, timing has been working in our favor.