getProfile().restingHeartRate return null

Very good solution, instead of correcting sdk garmin corrects documentation.

So from know if somebody report bug you add comment in doc, yes? I've reported 2 so now:

- setValue - ocasionally generate Error Name: System Error, as somebody describe in https://forums.garmin.com/developer/connect-iq/i/bug-reports/strange-error-from-era-on-some-devices

- using strings, load strings - on some device generates error

Error Name: Invalid Value
Devices:
    fÄ“nix® 6X Pro / 6X Sapphire / 6X Pro Solar / tactix® Delta Sapphire / Delta Solar / Delta Solar - Ballistics Edition / quatix® 6X / 6X Solar / 6X Dual Power: 15.40
    fÄ“nix® 6X Pro / 6X Sapphire / 6X Pro Solar / tactix® Delta Sapphire / Delta Solar / Delta Solar - Ballistics Edition / quatix® 6X / 6X Solar / 6X Dual Power: 16.60
    Forerunner® 245 Music: 5.70
Languages: cht, deu, eng, fin, spa

beautiful solution, as I understand you'd be glad if car manufacture send you correction in user guide if something break up in a car

Our 4.0 API docs state that this value may be null (this was not the case in earlier docs). It's currently working by design.

See my response in the original thread.

There's a user setting for resting HR (which can unfortunately be null), and UserProfile.restingHeartRate apparently reflects that setting.

I hate the fact that it's initially null, too, but I still want to be able to access that value, because that value is used for a couple of things on the watch (HR zones by HRR, and %HRR data field.)

You can't just change the definition of UserProfile.restingHeartRate to be something else (daily resting HR), because that breaks apps which rely on the current implementation (which include a couple of my apps.)

If you want daily resting HR in CIQ, then that would be a feature request for a new field. (e.g. UserPriofile.dailyRestingHeartRate).

I don't agree

1. getProfile().restingHeartRate is like every other counted values and what is important it's rather impossible to count it by user himself (it's counted in background by watch somebody has to observe HR values during my sleep).

2. So if it's counted it should be presented from CIQ.

3. If Garmin think that sometimes can be a better value it should give chance to change by user as:

- counted restingHeartRate

- average 7d restingHeartRate

- manual value

but never null

"In my opinion, this is working as expected,"

Sorry, I mean working as designed.