This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Bug report: Spectator Messaging broken / feature request

During a recent long ride (>14h) with LiveTrack enabled, I've noticed only later on that Spectator Messaging broke during the ride so that only few messages came through in the first half of the activity.

Since it is probably impossible to reproduce exactly, this is the set-up I was using:

  • Firmware 17.26 for Garmin Edge Solar 1040
  • Apple iPhone 13 (iOS 16.5) connected via BlueTooth
  • I was following a course (imported from Komoot)
  • LiveTrack and Spectator Messaging enabled (obviously)
  • No PowerGuide
  • I was actively stopping/starting the ride during breaks (so not just pausing)
  • Spectators were able to use the LiveTrack link and see my position and data until the end
  • Messages weren't visible on the device, no notification

My suspicion is that stopping the ride (instead of just pausing) broke the messaging while LiveTracking continued to work.

After this bug report, last but not least the feature request @garmin: Please make the spectator messages available with the activity. I was told that some of my friends went to lengths in sending motivational messages, so I'm sad to be unable to read them or thank them in the first place!

The link to the activity, if it helps: https://connect.garmin.com/modern/activity/11158807591

  • Same behavior on the 840. 

  • Update - the last few times this has happened I have force quit the Connect app and relaunched it, and then started getting messages.

  • Interesting, as this could point to a Bluetooth connection/app issue between mobile device (iPhone 13 in my case) and the Garmin. In the case I reported, the missing messages were showing the next time I booted up the Edge and had a WiFi and/or Bluetooth connection - days after. I would assume that this also supports a connection issue being the root cause.

  • I received a message from Garmin today that they have released a fix via the Connect app (version 4.68) and that they can’t reproduce the issue anymore. I’m going to give it a shot during my next ride but please do report back if you do!