Data Fields - Has anything changed?

Hi,

Has anything changed recently in the device firmware's in regards to Data Fields?

I am getting a string of users contacting me, on what started as the VAHR and now Edge devices, reporting they don't work. The Data Fields are long established ones (over a year old) and I haven't made any recent updates.

In the CIQ_LOG.TXT they get an Exception in compute, with a stack trace of null.

When I ask them to use a Test Build, it works perfectly, and generates no helpful Log.

I have a VA, Fenix 3 and Edge 1000 and can't repeat.

Any ideas?

Cheers
Chris

chrishares over 8 years ago

A thought on something you might try. (disclaimer: I've not done this myself, but I think it should work!)

The user that's having the 162.000000 problem. Have the user send you their .set files (or just the one for your DF if they know which it is - if not, you should be able to file dump the .set files and find the ones with your keys in it). Rename it so that it matches the .prg you run in the sim, and put it in the settings directory in the temp folder used by the sim. That way you might be able to run the sim, using what they have for settings and debug what's happening.

Thanks Jim - can you edit Set files to create a 162.000000 entry?

jim_m_58 over 8 years ago

Thanks Jim - can you edit Set files to create a 162.000000 entry?

.

You could put some code in your app to force it, with a setProperty() call.

Coleman.Apps over 8 years ago

This information is extremely helpful. Thank you so much! Do you know what OS your user's are using for settings?

Thanks,
Coleman

chrishares over 8 years ago

It is Android, as Jim expected.

It looks like whatever is saved in a Float Setting, is throwing an exception on .toFloat() and .toNumber()

Cheers
Chris

chrishares over 8 years ago

PS. It's not getting picked up in the Developer build, as the settings are not carried from the Live version, and they can't be changed in Garmin Connect - so basically the defaults.

Coleman.Apps over 8 years ago

After this was looked over by the team it looks like the code you were using was working fine until the GCM team fixed something about the way it was sending settings back to the device. You will likely need to add something to your source to handle this as this is due to a fix that the GCM team implemented and not a bug. I apologize for any inconvenience. Thank you again as always.

-Coleman