08-08-2019
04:27
- last edited on
08-13-2019
19:00
by
LizzyFitbit
08-08-2019
04:27
- last edited on
08-13-2019
19:00
by
LizzyFitbit
with the latest update i have not been able to change the time cues for running. i go in to reset it but the app just crashes and nothing has changed. i tried changing it on this page and seeing if it would sync up but it doesnt
Moderator edit: updated subject for clarity
08-14-2019
05:28
- last edited on
08-15-2019
09:43
by
AlvaroFitbit
08-14-2019
05:28
- last edited on
08-15-2019
09:43
by
AlvaroFitbit
Is anyone else having trouble with the app crashing when you change the exercise notification? After the last update the app reset my distance notification back to every mile, when I want it at every .5 mile. When I try to reset it back to .5 miles the app crashes. Every. Time.
Moderator edit: updated subject for clarity
08-14-2019 06:02
08-14-2019 06:02
@CB1207, welcome to the Fitbit Community! I hope you're doing well!
Let me help you with your Fitbit app not working as it should. For the first and third issues please log out from the app, restart your phone and log back in. For the second one could you share a screenshot of what you are seeing?
Let me know how it goes.
If a post helped you try voting and selecting it as a solution so other members benefit from it. Select it as Best Solution!
08-14-2019 06:03
08-14-2019 06:03
When I try to change the frequency of voice cues to 0.5 mi the app crashes and the change is not saved. The frequency can be changed to other distance settings or time settings and will not crash and the change is saved. Only changing to 0.5 mi causes the crash.
08-14-2019 06:49
08-14-2019 06:49
08-14-2019 06:51
08-14-2019 06:51
I’m having the same problem. What’s going on?
08-14-2019 07:37
08-14-2019 07:37
Don’t know. I can set other distances, 1 mi, 1.5 mi, etc and set time intervals as frequency but not 0.5 mi. And, of course, that is what I want.
08-14-2019 08:02
08-14-2019 08:02
08-14-2019 08:49
08-14-2019 08:49
I have the same problem, I think it started with the last software update.
08-14-2019 09:02
08-14-2019 09:02
08-14-2019 12:02
08-14-2019 12:02
Thank you. I had tried the logout/reboot phone a few times already, but I tried it again this morning. The exercise shortcuts that I had updated my macbook are now showing up in the app. However, the main issue, when I go into account settings, exercise tracking, frequency....I still cannot chose the distance based cue of 0.5mi....when I do, they try to go back a screen, the app crashes and I'm kicked back out to my iPhone home screen. When I select other options, like 1.0 mi or 2.0 mi or even the time based cues, the app accepts the change and doesn't kick me out. So I think there is still a problem with the Fitbit app. I have an iPhone 6S, so I'm hoping that is still current enough...my IOS is updated. Thank you!
08-14-2019 14:08
08-14-2019 14:08
Has anyone found a solution to this issue at this time?
08-14-2019 14:30
08-14-2019 14:30
08-15-2019 07:03
08-15-2019 07:03
On the IOS app, version 3.3.1 (on an iphone SE with a Fitbit Charge HR), when I click on the "weekly excercise" tile, then click on the stopwatch icon to start a run, then click on "Cues", then "frequency", if I try to set the frequency to 0.5 or 1.5 mi it leaves the app and takes me to a black screen and then my regular phone screen. All the other distance frequencies, such as 1.0 mi, 2.0 mi, etc., I can set fine. I've tried turning my phone all the way off and on again but it doesn't help. Anyone have any ideas? It used to work fine until around the time of the last app upgrade.
08-15-2019 08:31 - edited 08-15-2019 08:33
08-15-2019 08:31 - edited 08-15-2019 08:33
Hi CW,
There have been a few threads detailing this issue. I even provided a video but no one has responded, let alone, responded with a fix. So far, Customer Service has not addressed it. I doubt they have a clue.
Here’s a workaround. It’s not perfect but I was able to extrapolate enough data to analyze my run.
Go to where you would normally set you .5 cue. Scroll down to”Time Based Cues”. I was able to click and save without the app crashing. If you run a 10 minute mile, just click 5 minutes. I picked the closest minutes to my mile split. It was close enough to figure out my time/mile.
I use a Alta HR and up to date on ISO and Fitbit firmware. Good luc
08-15-2019 08:51
08-15-2019 08:51
Yup. I'm having the same issue. I even tried deleting the fitbit app form my phone and re-installing. No luck.
In addition to this problem, the other odd thing that began to occur around the same time, is the disappearance of my heart rate graph on runs. To be clear, if I play tennis or select the generic "workout", I still get the heart rate graph. The problem only occurs on runs.
Here's hoping Fitbit can fix this with the next release.
AB
08-15-2019 09:02
08-15-2019 09:02
08-15-2019 09:08
08-15-2019 09:08
I'm glad this thread is listed. I'm having the same issue as CW, (oddly enough with the exact same hardware and ios 3.3.1 version of app). I guess its an iOS release bug? 1grannyfanny mentioned other threads out there with same problem. Guess i'll eat into my morning and look for a few more to upvote too.
08-15-2019 09:12
08-15-2019 09:12
Hi 1grannyfanny, as you seem to know your way around the forum/community here... any links to other message boards addressing cue frequency? I'd love to upvote them as well 🙂
p.s. your solution to the issue (calculating your split) is a clever one, but I do like to use GPS for when i'm running different types of terrain. I hope they fix the bug!
08-15-2019 09:40
08-15-2019 09:40
08-15-2019 09:44
08-15-2019 09:44
Yeah I saw all that after I made my original post. Here's my read -- they are preparing to force us all to download a radically different version of the app, and don't want to waste time or money fixing bugs on the old version. We all realize that's unacceptable, however that is indeed my sense. I say this because a couple of days ago the app randomly tried to get me to convert to some new version, but warned me that the process was "irreversible." So I passed at the time, but wish I hadn't because now I can't find a way to do it. Not well managed...
AB