10-03-2017 09:16
10-03-2017 09:16
It used to work beautifully, but now more often than not I will get the red icon that I need to check my phone (Ipone 7+ IOS 11). I no longer get to see the map on my Dashboard nor any details besides how hard I ran during different terrains. Which is why I bought this unit for.
10-03-2017 11:46
10-03-2017 11:46
Today it indicated that it had synced before I started my run, then after my run, I had no GPS data. This is infuriating.
10-03-2017 11:49
10-03-2017 11:49
I believe there are more people having this problem than reporting it. I hope they come up with a solution soon, I'd hate to have to buy other equipment to get the information that I am looking for
10-03-2017 13:22 - edited 10-03-2017 13:24
10-03-2017 13:22 - edited 10-03-2017 13:24
I have an iPhone 6s with iOS 11.1.x. With iOS and using the battery "low powered" option, the phone will not track. When I hike/walk, I turn this feature off in the setup on the phone. (to the left on the toggle slider) This clears my connection problems.
10-03-2017 14:00
10-03-2017 14:00
I have the same problem since the upgrade to iOS11 (iPhone 6S). Before the feature worked without a hitch, and now all I get while running is the red phone symbol on the Blaze display and no GPS data whatsoever. 😕
10-03-2017 17:51
10-03-2017 17:51
My battery was fully charged and low power mode was not engaged. Other explanations?
10-03-2017 23:33
10-03-2017 23:33
Same here, I’ve had no end of trouble since iOS11 constant check app every time I try to use the GPS tracking for my rides or runs.
10-04-2017 03:20
10-04-2017 03:20
Same with me. I use this feature everyday after the latest update app will not connect to gps. I know others that use Fitbit have the same issue.
10-04-2017 04:33
10-04-2017 04:33
I had the same problem so i desinstall the program from my phone and restart my phone. After i reinstalled the program in my phone again and it worked. Maybe it could help you too!
10-04-2017 09:37
10-04-2017 09:37
It only worked temporarily. Worked for a full run yesterday after doing that but I had the same issue today.
10-04-2017 09:51
10-04-2017 09:51
I've done that too, and still same issue where sometimes it works and other times it doesn't. I even start my watch in an area that I know it can connect to my phone, start my run and then I get the red icon. Its very frustrating when you want this to work, and it doesn't Such a first world problem.
10-04-2017 16:19
10-04-2017 16:19
I reinstalled it after the first time the gps wouldn’t synch and it worked, but the next time I tried to connect it to the phone it didn’t work again. I hope they fix this cause I don’t want to have to buy another device!!
10-04-2017 18:57
10-04-2017 18:57
I am having the same issue. I did a chat with the tech support and it was a joke. Very disappointed. Mine used to work well too, but since the apple update it's not been working at all. I hope there is a resolution being worked on .
10-05-2017 01:39
10-05-2017 01:39
GPS issue here as well, Samsung Galaxy S7 edge with Android 7.
Connects to phone, with one or two bars, and drops out frequently during the run.
The phone is in my pocket, so range should not be an issue.
10-06-2017 05:27
10-06-2017 05:27
I bought the very first Fitbit when it launched, and have been in this ecosystem ever since. I have owned the Fitbit, the Fitbit One, the Flex, the Surge, the Charge, the Charge HR, multiple Arias, and now the Blaze. The warranty policies have always been excellent - Fitbit definitely stands by their products when there is a physical problem with the device, and it's within the warranty period.
I'm currently in a Ragnar challenge (7 summits, for anyone who is curious) that has some money on the side with a group of friends of mine. I'm out of the running because I can not get the GPS to work - my runs are not independently validated. I have done everything imaginable to reset the device and clear out any potential garbage data, doing multiple diagnoses and trying different things. I reset the Blaze. I deleted and reinstalled the app. I backed up and reset my iPhone. I disconnected and reconnected. Yesterday during a run the Blaze started okay then paused all by itself. Most of my run never got tracked.
I talked a lot of my friends into getting a Fitbit product. Most of my hardcore running friends have Garmins. They are gently mocking me right now because I can't get this thing to work, and I would do the same in their shoes. And it would be more funny to me if money were not on the line, and if I didn't feel like my time was "wasted" because I don't have a technical log of my fitness activities.
Fitbit does a lot of things well, and I love the sleep tracking and the HR. It's all pretty good. But I'm at the end of my rope here. I was going to buy an Iconic (i was planning on waiting for the Adidias version to see what that was about), but I'm losing trust in the product line because the lack of any acknowledgement of these issues. Furthermore, the lack of communication of a path forward to resolve these unacknowledged problems is both frustrating and undermines my confidence as a consumer. I am about mentally ready to rip off the band aid and move to another fitness tracker that meets my requirements for reliability and consumer engagement.
10-06-2017 06:18
10-06-2017 06:18
I turned on Bluetooth sharing (which I have never turned on before) and the GPS started working again. Not sure how long it will work but this is the first time it has worked since the last iOS update. Try it maybe it will work for you too.
10-06-2017 06:31
10-06-2017 06:31
Just had same issue. Tried to start my run using my blaze watch but ‘check Fitbit app’ error. So decided to use my app as well as my watch to do my run. Both displayed different times! Personally I think the app time was more accurate than the watch. This is so frustrating. Needs fixing.
10-06-2017 13:24
10-06-2017 13:24
so today there was an IOS update to it, and bluetooth sharing was already on. But I will test tomorrow like I have the rest of this week already. Last night I did tell it to forget this bluetooth device and reconnected it... so maybe that will help
10-06-2017 13:27
10-06-2017 13:27
I am in the same boat with you. I'm thinking of biting the bullet and getting an apple watch.
Like you i had the 1st fitbit, and loved it. I had a garmin vivofit, but liked what the blaze offered and switched to that. Now I'm not so sure I should have done it.
Just really frustrating. Hopefully there is some resolutions soon.
10-06-2017 13:29
10-06-2017 13:29
I was really hoping that Fitbit would chime in at anytime and give a response of "hey we know something is going on and we are working on it" But nothing.... I feel your pain, especially being called out on a race that you have been training for. On my training runs i use the strava app and my Blaze and take the results for what they are... Lets see how long I can hold out before I bite the bullet and buy another device to do the job right.
I have been standing behind Fitbit this whole time because I dislike the Iwatch so much for all the things it does do, but for sure it would do a much better job right now.