Live event sharing - LiveTrack link is missing from message content

LiveTrack link is correctly created and shared with e-mail.
However the link is missing from Live Event Sharing message even I turned on 'Share Location' option.
Is this an expected behavior?


Top Replies

All Replies

  • I've noticed this too. Live Track works as expected with a link sent to email. Live Event, however, just sends a text but no "Track Me" link as described in the example text.

    I recommend reaching out to Product Support through their website at https://support.garmin.com. 

  • , I opened a support ticket using chat. They are stating that this is a known issue and will be fixed with a software update. No timeline of when this should happen. Transcript below:


    [9:15:32AM] Garmin Support: So the contact gets a message with sharing but not the track me option?
    [9:16:15AM] seilogramp: Correct. The text for Live Event Sharing comes through as expected, but no link to click on.
    [9:17:21AM] seilogramp: I'm on Garmin Connect Mobile Android version 5.6.
    [9:17:42AM] Garmin Support: Can you upload a photo of what you are seeing here?
    [9:19:38AM] seilogramp: done
    [9:29:53AM] Garmin Support: let me see if I can find anything here
    [9:33:07AM] Garmin Support: Okay great, I did find a case here with a few customers with the same issue, sounds like it should be fixed with a software update here before to long
    [9:38:28AM] seilogramp: OK sounds good.
    [9:38:43AM] Garmin Support: have a good day!

  • I received an email today from Garmin Product Support stating that this issue was resolved with the latest update of the app to version 5.7

    Hello,

    We're following up on the report we received that after starting a Live Event Share with LiveTrack enabled, your Track Me links weren't being sent. We're pleased to report that this issue has been resolved with the 5.7 release of the Connect app, which is available now through your Google Play Store. Please update your Connect app and you'll no longer experience this issue.

    . I have confirmed that it is indeed fixed.