Vivoactive HR Not Setting Properties

Hi,

Can anybody help me with this, otherwise I am going to have to pull support for the Vivoactive HR.

The code I am calling, which is working on the Vivoactive, Epix and 920XT is:
App.getApp().setProperty("property", "value");


However all VA HR Users are saying it's not saving, and they are back to default settings.

I've requested log files, and they contain nothing useful.

Thanks
Chris

Follow up:

Would somebody on this forum be kind enough to help?

I can provide a Test Side Loaded version, and just need to see if it generates any errors; not that the App is crashing.

Asking Users is providing difficult, as they are struggling with the concepts of side loading, and getting me the correct log files back.

Thanks
Chris

If they get an error when trying to just do settings from a phone, are they running the 2.62 beta FW? You can't get into settings with that right now. You could also ask them to try from GE.

Also, there are some things about Android CGM to look out for:

https://forums.garmin.com/showthread.php?341818-Issue-debugging-settings&p=795298#post795298

As far as sending them sideloads, you can't do app-settings with sideloads, so they can't do app settings with those.... It needs the .json part from the app store.

Thanks Jim

Sorry, I should have made it clear. The problem is occurring on two Apps, which have their own hand rolled Settings Page which uses getProperty and setProperty to load and save settings.

I have a Vivoactive, which works correctly and the Simulator (all being it's a simulator) also works correctly on all devices.

Therefore something is happening on the VAHR only which is stopping the getProperty or setProperty from working. In addition, the application is not crashing, and based on the log files sent from Users, generating an error message.

Cheers
Chris

Thanks Jim, sorry I am not sure which one I am using!

I am calling
- (Object) getProperty(key)
- (Object) setProperty(key, value)


From Toybox::Application::AppBase

Does that make sense?

Cheers
Chris

I am getting more complaints about this now. Unless I am find a solution, I will have to pull the Vivoactive HR version, to avoid negative feedback.

In summary, the Vivoactive, 920XT and Epix versions of the same App work correctly. The App saves user preferences using getProperty and setProperty.

I have a Vivoactive and it tests perfectly. Also, the simulator in all versions (including VA HR) also work. None of the VA HR users report any crash, just no settings remembered.

The CIQ_LOG.TXT from the VA HR is reporting nothing.

Need some help urgently please!

Cheers
Chris

I can't reproduce this on 2.65 with our ObjectStore sample, which we use to test getting and setting properties. I was just looking at the change log, and there was a fix included in 2.65 that was not in 2.64, which I think addresses the problem. I mentioned that there was a similar issue on fenix 3, and this fix also addressed the fenix 3 trouble.

I don't know whether you should advise customers to use beta quality firmware, so it might be a good idea to temporarily suspend VA-HR support and wait until we have a non-beta firmware release.

- deleted -