Garmin Edge 510 Won't Sync With iPhone 7

[Happy2BRiding]

I recently updated the Garmin Connect app (v4.25) on my iPhone 7 (iOS 13.2.2) and now for some reason my Edge 510 will not sync.

It connects via Bluetooth just fine so that is not the problem and I double checked to make sure I have Auto Upload turned on but still after every activity I get a sync failed message. I tried disconnecting "Forget this Device" in the Settings app on the phone and removing the device in the Garmin Connect app and running through the process of reconnecting it to both but that did not solve the issue.

Anyone else experiencing this problem or have any suggestions for how to fix it?

Edit: I just found this. I'll give it a go and see if it works.

https://support.garmin.com/en-US/?faq=9 ... asLarkUvH6

[The RideR]

I'm not sure if that will help since I'm using Android phone, but every once in a while I have to erase my older rides from Garmin to be able to upload new ones via Connect. Try deleting 10-20 records and see if that solves the problem.

[Happy2BRiding]

I'm not sure if that will help since I'm using Android phone, but every once in a while I have to erase my older rides from Garmin to be able to upload new ones via Connect. Try deleting 10-20 records and see if that solves the problem.

Good tip but I agree I don't think it will help with my issue. However I do find if I don't hook my device up to my computer every month or so and dump all the activity fit files to my hard drive I occasionally run into quirks with it either not saving my ride or the ride file getting corrupted. So I definitely do what you're suggesting on a fairly regular basis.

On another note I see Garmin has pushed out yet another app update (v4.25.1) for iOS overnight last night so I'll install that and see if it helps.

[countryboy_mike]

I had to delete my Garmin Connect App, unpair my phone then reload/pair everything. This happened after the last couple of software upgrades to the Iphone.

[Happy2BRiding]

Updating the Garmin Connect app to 4.25.1 solved the problem.