WTH Garmin, why did you do that, and at the same time, why didn't you document it???

For some stupid reason, above 10K steps, the Steps Complication is no longer a Number but becomes a Float and divided by 1000, so 15,500 steps becomes 15.500. And of course, it's undocumented, sigh.

WTH did you do that for???

Oh, and BTW, you can't test that in the Simulator because the Steps returned by the Complication there becomes bunker (a very, very large number) above 10K.

jim_m_58 over 1 year ago

Which target? With a 965, I see it jump to 1 billion. Always a Number, never a Float.

Looks like a bug in the sim to me and the doc is correct. ActivityMonitor.getInfo().steps is correct though.

SylvainGa over 1 year ago in reply to jim_m_58

On my Venu2, it turns into a float at I'm assuming 10K. I had 15351 steps earlier today and it displayed 15. Through a debug line dumping the value in the log file, I saw the complication value was 15.351, not 15351.

This was first mentioned to me by a user with a Forerunner 955 Solar. He was at 11K steps and it only showed 11 on the watchface. Again, that's through Complication. No issue if read through ActivityMonitor,

jim_m_58 over 1 year ago in reply to SylvainGa

So something is wrong in the FW for at least some device. I was testing in the sim.

As a work around, I'd just display steps from ActivityMonitor until this is fixed. You can still launch the glance with onPress.

Could be on the actual device, having a float is a trigger for showing "<something>k" if it's above 9999 steps with a native WF.

SylvainGa over 1 year ago in reply to jim_m_58

Could be. I'm doing an instanceof and if it's a Float, I multiply by 1000 and convert to a number. They should leave it to the dev to show as K or not, or at least, document it properly!

If it's a bug, where should it be reported? Dev Bug report sub or the device specific sub? Both?