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

[Midorinoji]

The problem is not with iOS 13.5.1 compatibility. The current heart rate was showing in the app after upgrading to 13.5.1. For me it stopped only after upgrading the app to 3.24.1 on Friday last week. Although I upgrade manually , this time I made the mistake of upgrading before looking at this site first to see if anyone was having problems. I usually look at that figure several times a day and prefer to do so in the app rather than on my Inspire HR because of the size so noticed very quickly.

This is not just a problem with the current heart rate but with syncing in general. I have all day sync turned on but the app only sync's when it is first opened or done manually. Even if the app is active and the screen kept unlocked none of the data updates at all.

This is not the first time this has happened. There was a similar problem back in May which was acknowledged (and maybe not properly fixed).

From the responses in this thread it doesn't even look as if anyone at Fitbit has tested this to see if it is a general problem although there are enough people saying they have the same problem in a short space of time to suggest that it is affecting a large number.

[robsterc]

@Midorinoji 

Thanks for this. It works as you say temporarily and the big plus is not having to reinstall the app. 

I agree it's wider than heart rate data and on mine too it's as wide as synching in general. 

I hope Fitbit support are working on a fix but there is no easy way to alert them to bugs in the software. For instance there is a more cosmetic bug when you hit the text to return to the previous screen in the app where the text vanishes and you stay in the same screen. You then need to click the back arrow to actually return to previous screen. I'd let the devs know if there was a convenient way to do that.

[robsterc]

@ChasBFit 

Thanks that works for me and is far less intrusive than uninstalling and reinstalling the app. Temporary fix though as you say as it stops working after some time but easy enough to flip that all day sync setting.

Hope they have this in the list of fixes they are working on.

[Michaela.W]

Charge 3 was working fine with my iPhone SE until Fitbit updated the app. I uninstalled the app, reinstalled it, and then found the work around of flipping the All Day Sync. But today that option has disappeared??! Have updated to latest iOS 13.5.1, restarted Fitbit Charge 3 by charging and holding button for 8 seconds, and it works showing current heart rate, I come out of the app and look at Facebook then back to Fitbit app and it’s back to Resting heart rate!! 
I think having to restart the Charge 3 each time to view heart rate is too much and Fitbit needs to fix their iOS app. Maybe it was a little of my fault as I had auto update turned on for Fitbit, but Fitbit is at fault too!

[SunsetRunner]

Until they get this fixed, my work-around is to alternate All Day Sync off and on. It works once, then I have to change it again. Definitely not a long-term solution. To clarify, if it's Off, I turn it On, if it's On I turn it Off. Makes no sense but it works. At least that's easier than uninstalling/reinstalling the app, which is what I did the first time. That was a waste of time and effort.

[LizzyFitbit]

Hi everyone. It's good to see you around and welcome to our new members. I'm sorry for the delayed response.

Thanks for sharing detailed information about this situation and the steps tried on your own. I understand how important for you is to have your current heart rate available on the Fitbit app and I'm sorry for this inconvenience. Let me share that our team will release the Fitbit app version 3.25 very soon and I'd recommend to download it in your iOS devices as it'll bring improvements for the app.

If by any chance the issues persist and just if you've not done so, please provide me with the model of your iOS devices and the iOS/software version so I can look into this.

I'll look forward to your reply.

[Midorinoji]

@LizzyFitbit 

Thanks for the information but this is the usual vague Fitbit response which simply looks like standard policy rather than something specifically addressing this issue.

There are two questions which need to be answered:

1. Have the development team found the cause of the problem?

2. Do they believe that it has been fixed in version 3.25?

Just saying the new version has "improvements" says nothing. As with any version there is the risk that new problems will be introduced. That risk may be acceptable if we can be confident that the problem has been fixed but there is nothing in your post which suggests it has been addressed.

[Shyam]

Hi Michaela:
I think the problem has to lie with the Fitbit app. Now in a later e-mail Lizzy wrote that a an updated version of Fitbit was coming soon but there was no date as SOON is vague.

Let’s hope the new version comes out soon!

Shyam


Get Outlook for iOS

[Shyam]

Hi Lizzy:
When is the new version coming out as “soon” is vague.

Now my Charge 3 does not get connected to WiFi quite often but I will figure it out to get this done.

Cannot wait for the 3.25 to come which I hope is compatible with 13.5.1.

Shyam

Get Outlook for iOS

[Shyam]

It appears that we will need to wait and see if 3.25 will take care of all our problems. It is definitely getting frustrating since now my Charge 3 does not connect to WiFi but I know I will figure this out as this has happened tome recently. If it’s not one thing it’s another.

Shyam

Get Outlook for iOS

[robsterc]

@LizzyFitbit 

Thanks for the update, I had been beginning to think that Fitbit support weren't going to make any more replies.

I'll back the comments from others on this thread that it isn't clear from your post if 3.25 will specifically address this bug and if it does when it is projected to be released. Are you able to supply more information?

[jillnicesteppin]

The All-Day Sync option has disappeared from my app, as of yesterday. 😞

[jillnicesteppin]

@LizzyFitbit 

The All-Day Sync option disappeared in my app as of yesterday. Will that be restored in the next version of the app?

[Sharyn66]

I have removed the FitBit from my app, rebooted my phone.  There is no option for all day sync on my Alta HR.  I have the latest version of the app.  Nothing seems to be working, but the main reason I use a fitbit is to check my HR during exercise.  Which now I'm unable to do.

[MrMarv]

@LizzyFitbit -

I updated to iOS app version 3.25 approximately 24 hours ago. 

The halting of dynamic update to the "Today" screen continues. It actually lasted approximately 2.5 hours today before the app just stopped updating. Attempts to sync show a progress bar that stops halfway across the screen, stays there for close to a minute (haven't timed it - uncharacteristic of me, huh?) and then stops the attempt. 

So, unsurprisingly with my Bluetooth pairing issues, the 3.25 update didn't do a thing for me - maybe others will benefit, but not MrMarv.

Regards, 

Marv

[Shyam]

Hey Marv
My Fitbit version is 3.24.1 and when I check for any update, I get the message that my charge 3 is up-to-date and I cannot download 3.25.
Thanks for your update.

Shyam

Sent from my iPhone

[Midorinoji]

I can't say I'm surprised it's not fixed. The lack of an answer to my question to @LizzyFitbit 

about whether the Fitbit team thought they'd fixed it left me thinking the information about the new version was just a platitude.

Interestingly 3.25 doesn't seem to be available to me yet. Maybe availability is phased by region.

@MrMarv 

Have you noticed any new problems or benefits in 3.25? If it doesn't fix the updating problem I'm not sure if I'll bother to update when it does become available where I am.

[MrMarv]

@Midorinoji -

Haven't seen much difference between 3.34 and 3.25, but I've only had it installed for about 26 hours.

And today was a bit full with "things" around the house this morning and an afternoon with my Grandson in the park - definitely more important that trying to figure out where the FitBit developers have done something right, or not.

[robsterc]

@MrMarv 

No 3.25 update showing on my phone yet, but probably is deploying by regions. 

I'm disappointed that 3.25 appears not to fix the issue, but not surprised as we've had no confirmation from support that the bug was being squashed in this update. It would be great if we were able to see which bugs are being fixed in forthcoming updates.

[MrMarv]

@robsterc -

I gave up on the rolling update logic of Fitbit's. I routinely check the app store for updates a couple times a week.

Release 3.25 hit the app store on the 10th, four days ago.

The "official" release post here on the board is from 14 days ago for release 3.24.1. I don't remember when it hit the App Store, but it was quite a few days before that.

As a developer, and one who, a long long long time ago coded to the Windows mobile environment and DOS/Windows for "fun" and a little bit of pay, here and there, I can understand why release notes are so "slim" when it comes to information.

I can understand, but I don't have to like it.

It is commonly done for one, or more, of three reasons - 1) hackers target changes, as they are perceived as not being "bullet proof" yet, 2) the developers are not confident of the new enhancements/fixes and/or 3) management wants to hide embarrassing "things".

And FitBit is not the only one. I have been a developer for over 40 years. Once upon a time, Microsoft used to clearly and verbosely state what was new and what fixes were incorporated into first DOS and then Windows releases. Then the specific targeting by hackers started and update documentation started getting smaller and smaller. 

Just a nature of the beast.