Fenix 5 series and SDK version 2.2.5

Hello. It seems that there are a lot of dysfunctions with the SDK 2.2.5 and the new Fenix 5 series.
I developed a lot of apps like WF and they run fine on all the watch models. Since the Fenix 5 came out, I encounter a lot of compatibility problems for some of the basis functions of the API. For example, it seems that:
- getHeartRateZones does not work, the array is always null
- setProperty: impossible to set a property, the app crashes
- retrieving some data from an activity, like getActivityInfo().currentLocation: no data at all while it is used for other calculations
- same with activityMonitor, to gather, for example, the HR history, the app freezes after a while
and so on...
All of these functions run well in my apps on all the previous watch models, except with the new Fenix 5 series and this SDK 2.2.5.

What's wrong with that ?
Thanks for your response.

jim_m_58 over 8 years ago

I use setProperty in a number of apps that I know run on the f5 that were build with 2.2.5. In most cases I'm writing to the Object Store (the .str file), but in one case I update the settings file (the .set) and not seen any problems in either case.

For ActMon.getHearRateHistory(), I uses that in most if not all of my watches, and when built with 2.2.5, have had no problems (or reported problem) of f5 devices.

(I don't do the other things you mention in your post)

It kind of sound to me that something else might be going on, and what you are seeing may just be a symptom. You may want to provide the info in standard bug report and either post your code or email the code to Garmin.

Surfy66 over 8 years ago

Thanks for your response Jim. I forgot to mention that when I launch the app in the simulator, everything works fine... The app is totally functional.
And the problems reported where encountered on Fenix 5x, I don't know if they happen on Fenix 5. Finally, when I want to see what's going on by viewing a log file, the app does not generate one, no file at all, as if there was no issue. I can't understand because the behavior seems to be totally different than the previous models with previous sdk, where each error was reported in a log file, not currently with Fenix 5x for some issue.

Former Member over 8 years ago

Surfy66,

I've sent you a PM. I'd like to try and see if I can reproduce this on my end. Please see details in PM.

Thanks,
-Coleman