You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Long story short, I'm ending up with Moments backed by a floating point type (rather than an int type) when running on sim. This leads to truly bizarre results, arising from what I believe is epoch times being stored in single-precision floats, then experiencing loss of precision due to the magnitude of the values involved.
Long story short, I'm ending up with Moments backed by a floating point type (rather than an int type) when running on sim. This leads to truly bizarre results, arising from what I believe is epoch times being stored in single-precision floats, then experiencing loss of precision due to the magnitude of the values involved.
See https://forums.garmin.com/developer/connect-iq/f/discussion/354859/monkey-business-in-data-types-used-by-moment-internals.
Seeing this issue on sim only, while Moments on real HW seem to cast-to-int in their constructor.
Workaround:
The text was updated successfully, but these errors were encountered: