Mapshare tracks show on mobile phone but not desktop

Former Member
Former Member
My mapshare tracks show on my mobile phone and tablet, but do not appear on a desktop computer or laptop. I am using the same browser on each (have tried with Chrome and IE). Does anyone know why this might happen? Both worked fine a few weeks ago but something seems to have happened to make it dissapear on desktop computer/laptop. Here is the page: https://aus-share.inreach.garmin.com/TheLongWayHome
  • Just checked this on Chrome, Win10. I see track points for a large number of tracks, with track points and lines visible. Only checked back as far as May 13, but everything back to there is working fine as far as I can see.

    I get the same results with Safari on an iPad, both for the mobile and desktop sites.

    The only thing I can think of is to look at the right side of the blue user ID block in the left sidebar. You will see either a circled plus-sign or a circled minus-sign. If you see a plus-sign, click it. This control suppresses the tracks for the user to which applies.
  • There seems to be a bug in both map pages https://inreach.garmin.com/Map and https://share.garmin.com/share/xxxxx. I can see tracks only if I use 'Map Filter' to set 'Date & Time Range'. If date range is set to 'All Time' nothing is shown.

    If I debug web page I can see error message 'Map Connection Error: Error: Could not convert string to DateTime: 0000-12-31T22:00:00.000Z. Path 'StartTime', line 1, position 100.' That gives indication that web pages are somehow conflicting with my regional settings.
  • Former Member
    0 Former Member over 6 years ago
    If I debug web page I can see error message 'Map Connection Error: Error: Could not convert string to DateTime: 0000-12-31T22:00:00.000Z. .

    Although I am not an Inreach user, this post caught my attention and made me look at the Wikipedia subject of GPS system Epoch(s) again. Please note that the above quoted file does not appear to have a contemporary capture date embedded. It does seem that the original Jan 01, 1970 beginning of the full Unix-GPX epoch may not necessarily be used on modern navigation device data logs in all cases.


  • Looks like issue has been fixed. Tracks appears on maps correctly.