12-03-2017 12:15
12-03-2017 12:15
I went out for a run yesterday and was disappointed when the fitbit app kept asking me to turn on LOCATION ACCESS settings when I already had it set to "always". As a result Blaze gives me a "Check fitbit app" message and doesn't link to my phone. Oddly enough, GPS still tracked my run both times but the info on my watch and the app were not in sync. Today I turned both my phone ad my Blaze off and back on again hoping it would make a difference but it didn't. Same result as yesterday. I understand there are issues between iOS 11 and the Fitbit and have read workarounds but would appreciate any help anyone can give me because all this is doing is created frustration and stress - something I usually use running to get rid of so you can see I'm in a catch 22!
12-05-2017 15:49
12-05-2017 15:49
It's great to have you here @Faye1960! I'm sorry for the issue you've had with your Blaze and connected GPS. This type of error message usually appears when you need to grant location permissions on your phone or change a setting in your Blaze. You may want to double check that you have all the requirements in this article Why isn't GPS working?.
Also, please try to restart it and force quit your app.
Hope this helps! Keep me posted.
Want to get more active? Visit Get Moving in the Lifestyle Discussion Forum.
12-06-2017 06:41
12-06-2017 06:41
When this happens to me, I simply revoke location access to Fitbit then do a sync. It will then ask for access and permission.
It has only happened twice to me.
12-06-2017 07:04 - edited 12-06-2017 08:32
12-06-2017 07:04 - edited 12-06-2017 08:32
Thank you for your reply Silvia. I assumed this would have to do with permissions on or settings but they are set correctly and I have done everything outlined in the article. It isn’t a case of the GPS NOT working because my run is still tracked .. it’s a case of the Blaze not recognizing the app and a message continually popping up to ask if I want to turn on location access even though it already it! I have also tried restarting both the app and the Blaze.
12-06-2017 07:20 - edited 12-06-2017 08:31
12-06-2017 07:20 - edited 12-06-2017 08:31
Thank you for the suggestion Rich_Laue. I was hopeful this would work but sadly it didn’t