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
I am having an issue where the tool is completely crashing if it doesn't detect the speed right away (when it reads a new email/session before the watch's GPS kicks in). Shouldn't this just be setting it to 0 if the speed isn't defined yet?
[9/18/2024] [11:01:48 PM] [Core] » i info Fetching https://livetrack.garmin.com/services/session/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/trackpoints?requestTime=1726714908248
D:\LiveTrack-OBS\garmin-livetrack-obs-master\garmin-livetrack-obs-master\index.js:76
latestData.speed = latestData.speed || 0;
^
TypeError: Cannot read properties of undefined (reading 'speed')
at Timeout._onTimeout (D:\LiveTrack-OBS\garmin-livetrack-obs-master\garmin-livetrack-obs-master\index.js:76:35)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Node.js v20.17.0
The text was updated successfully, but these errors were encountered:
I am having an issue where the tool is completely crashing if it doesn't detect the speed right away (when it reads a new email/session before the watch's GPS kicks in). Shouldn't this just be setting it to 0 if the speed isn't defined yet?
The text was updated successfully, but these errors were encountered: