Current heart rate not being displayed in iOS app

[robsterc]

I've got all day sync activated and the app is current. If I quit the app and re-open it works for some time and then just shows resting heart rate.

It is recording heart rate as the graph over time updates. It just doesn't show current heart rate.

Any ideas?

Moderator edit: subject for clarity

[robsterc]

3.32.1 didn’t work for me either. A brief time it showed current heart rate and now back to resting only.

I’ve had no response so far from Fitbit Support to my escalation into this issue so maybe they haven’t been looking at it before!!

8 releases is a lot of opportunities missed by Fitbit to sort this out.

[ChasBFit]

Welcome to version 3.33, whiich STILL does not fix this problem. Disappointing, but unsurprising.

[Shyam]

Agreed that 3.33 does not fix the problem.
I have said this before that maybe this problem is not fixable.

Shyam

Sent from my iPhone

[MrMarv]

I was only able to "fix it" by replacing my Versa 2 - I walked into Best Buy with copies of both my first support email and the last one dated 6 months later and walked out with a new device right off the shelf.

[SunsetRunner]

---

@Shyam wrote:
Agreed that 3.33 does not fix the problem.
I have said this before that maybe this problem is not fixable.

---

I think that is extremely unlikely. This functionality used to work. If it had been broken by Apple in an iOS update then it would not work for any device and Fitbit would be quick to tell everyone it is not their fault and that they do anything about it. The lack of a comment suggests that either

a) they realise this is their problem but don't want to fix it for some reason that they don't want to talk about or

b) they haven't been able to find the cause (maybe because they are not working on it) or

c) don't care and therefore haven't put any effort into identifying the cause

@MrMarv wrote:
I was only able to "fix it" by replacing my Versa 2

---

It's good that you no longer have the problem but the "fix" may have just been coincidence. As I mentioned in an earlier post, I also go a new device under warranty but it didn't fix this problem.

[Nng414]

I continue to have this annoying issue.

Sent from my iPhone

[robsterc]

I had such a frustrating series of exchanges with Fitbit support about the combination of this issue on the app and the loss of accurate GPS after the most recent firmware update for Charge 3 which I suspect was optimised for Charge 4 at the expense of the legacy Charge 3. As a result I requested a return under UK consumer law. Fitbit refused and eventually wouldn't reply to the request but luckily I had purchased it via a high street store who saw the months of hassle trying to get fitbit to fix it and agreed a refund.

As a result I no longer have a fitbit device and have switched to Apple watch. 

I was so frustrated that Fitbit never said when they might get around to fixing the issue. It seemed that it would be never!

[MrMarv]

@robsterc -

Sorry to see that you had to go down the same "Customer Service Road of Uncaring" that I did and then have things worsen with the latest app update. Luckily for me I was able to get a replacement Versa 2, though I nearly went for a Series 5 as well.

What kept me with FitBit was the device/app combination whereas Apple has never brought a full service app to the table in Apple Health and the Watch app, at least to my knowledge. I was also a little concerned about the battery life, but not as much.

Good luck to you and be well.

[robsterc]

thanks @MrMarv 

I agree the Apple watch route wasn't what I wanted to do particularly given the battery life, but in the end the lack of action from Fitbit support was the overwhelming factor.

All the best to you and I sincerely hope that your Versa 2 continues to work well with the iOS Fitbit app.

[Iaina]

Thanks for doing the groundwork, all. Looks like I’m abandoning Fitbit for an Apple Watch as well...

[KateFitbit]

I'm closing this thread as it was an older issue that not appears to be going off topic. If you are experiencing this issue now, please ensure your app is up to date. Please start a new thread with screenshots and the device you are using.