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

Since update 5.22 Garmin Connect mobile app wil not send courses to my Garmin edge 1040.

Since update 5.22 Garmin Connect mobile app wil not send courses to my Garmin edge 1040.

When I select a course in my Garmin Connect mobile app (Android) and try to send it to my connected device Garmin Edge 1040: no popup screen and no course in my Garmin Edge 1040. 

BT connection is ok. When i select a ride in "Activities"  sending it to my device works fine. 

  • Please test your software before rolling it out 

    You're at least the 4th report I've seen of this issue, all with different Garmin devices. However, it's working ok for me so there's obviously some intermittent or configuration issues which means it might have worked ok in testing. 

    Also, in the future please display on watch once a course was successfully received.

    This would be a great idea. It would save having to go into the list of courses to check. 

  • I can import my gpx in the Connect app, save it, and than push the button to send it to the Edge.

    In the next screen i see my Explore 2, connected.

    When i push it, i return to the course-screen without sending it to the edge itself. 

    I already re-installed the Connect app, bluetooth on and off, cleaned the Edge Explorere 2, but no change 

  • Thanks for the report,  . I'm having this looked into now. Once we have some meaningful updates or if additional info is required, we'll circle back to this thread.

    Others experiencing this same thing, please bookmark this thread for updates.

  •  - I'd like to email you to gather some additional info. Do we have your permission to do so?

  • Same issue with my Fenix 7x and Edge 530 (connect 5.22)

  • No problem go ahead

  • I have the same problem, app wil not send courses to my  Fenix ​​7Pro and Edge 840. Garmin connect app version 5.22.

  • There is a new update for Android Connect to version 5.22.1 to resolve this. Please make sure to update your Connect version to 5.22.1 and if you are still experiencing this issue on the update, please create a new thread.