Acknowledged
CIQQA-3771

UserProfile.walkingStepLength is incorrect in sim; sim behaves as if units are cm, but real units are mm (as per docs and real device)

SDK: 8.4.0 / Windows (this problem also existed in 2023)

Real device: Forerunner 955 (latest beta firmware)

Simulated device: fr955

Recreation procedure:

- Create simple data field which simply returns UserProfile.getProfile.walkingStepLength in compute()

- Run data field in sim

- Data field will display 90 (90 mm = 9 cm)

- The default step length in the sim is 90 cm

Clearly walkingStepLength in the sim behaves as though the units are cm

- In Connect app, set custom step length (Settings > User Settings > Custom Stride Length) and sync with watch

- Sideload data field to watch

- Note that the data field displays the correct value for the step length (in mm). e.g. if the custom step length is 1 m, then the data field displays 1000 for walkingStepLength.

See also:

 RE: So walkingStepLength is in mm or cm?  

https://developer.garmin.com/connect-iq/api-docs/Toybox/UserProfile/Profile.html#walkingStepLength-var 

I think it says a lot about CIQ that someone brought this up in 2023 and absolutely nobody noticed or cared (this includes other devs in the tiny community).

flowstate

  • This is a simulator bug, but in my experience from last night it's not exactly what you and others reported:

    When you 1st open the simulator and start to log the value of UserProfile.getProfile.walkingStepLength then you see it "in cm" - meaning the value is 1/10th of what you expect to get based on the UserProfile settings (in the simulator).

    But if you then SAVE the User settings in the simulator (doesn't matter if you change the previous value or keep it - which BTW is in meters or feet, just to add even more units and confusion ) then the reported value in the simulator becomes the expected value in mm.

  • Oh btw this bug was already reported in 2023 and confirmed by a CIQ team member.

     walkingStepLength runningStepLength doc bug 

    (Ofc the actual bug isn't in the docs, but in the sim.)

    I'll be sure to check back in 2033.

  • Also I noticed that:

    - before ever setting a custom stride length, the value of walkingStepLength was null (so far so good)

    - after setting a custom stride length, walkingStepLength was a non-zero Number (still good)

    - after disabling the custom stride length in Connect, walkingStepLength is now 0 (hmmmm)

    It makes me wonder if something is broken now (i.e. that now I somehow actually have a custom stride length of 0 in practice that I'll never be able to get rid of). I mean it's probably nothing, but it's still disconcerting.