Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

GPS runs showing as straight lines and Inspire won't sync

Replies are disabled for this topic. Start a new one or visit our Help Center.

Hi there,

 

My Inspire HR Was working perfectly until I updated to the latest version of the app on iPhone X iOS 13.4. Since the update, I’m having two main issues:

 

1) Fitbit won’t sync unless I completely close the app (not just exit but swipe app on the list of open apps), it says “Failed to Sync” unless I do this. 

2) My cardio (runs and walks) suddenly started showing as straight lines on the map. The rest of the data seems correct (distance etc) but it just shows as if I went from point A to point B in a straight line, which is not the case

 

 

Moderator edit: updated subject for clarity

Best Answer
0 Votes
2 REPLIES 2

@Beholder69 Welcome to the Fitbit Community! It's great to have you here!

 

Let me help you with your Inspire not syncing and your GPS maps being incorrect. You can try the following:

 

  1. Go to your phone's bluetooth settings and remove all devices listed there.
  2. Restart your phone and restart your device
  3. Check that no battery saving app/feature on your phone is affecting your Fitbit app.
  4. Also, on an Android device, check that your app has the necessary permissions (settings > apps > Fitbit > permissions) and make sure bluetooth and location services (GPS) are on. 
  5. You can find troubleshooting instructions here and here for the GPS data.

Let me know how it goes.

Alvaro | Community Moderator

If a post helped you try voting and selecting it as a solution so other members benefit from it. Select it as Best Solution!

Best Answer

Thanks, Alvaro!

 

Restarting both devices seems to have fixed the sync issue.

 

As for the GPS, I found some advice in another thread saying to lock the phone while you have the app open (nice workaround but shouldn’t have to do this to get it to work) and my last 2 runs we’re showing properly. 

Not sure if it was the workaround that did the trick or the restarting, next time I’ll try running with the app on the background instead of open and see what if it has been fixed and then update. Thanks again!

Best Answer
0 Votes