Fitbit app crashes with new app update (3.39) when using an iPad

[xJennKAx]

With the recent update, my first generation Versa takes longer to sync and the app just doesn’t work- I’m not getting sleep scores, I can’t view any of my information. 

Moderator edit: subject for clarity 

[Kaylee3]

I think it is something with the iPads I tried to use a separate iPad but I was still having the same problems 

[SunsetRunner]

Funny part is my fitbit app worked on my iPad pro with no issues until I added my Fitbit Sense watch yesterday then it all went to pot as I cant do any settings on the Fitbit sense watch with the iPad. And then today everything acted up 😕 

[Daveleeander]

It doesn’t work on IPhone either

Sent from my iPhone

[Daveleeander]

😂 Apple problem eh? My iPhone 10 works just fine. Fitbit put an untested update out to the masses and screwed everyone. I’m thinking that Apple Watch works better than Fitbit anyway

Sent from my iPhone

[SunsetRunner]

its fully a Fitbit issue I agree on that. My IPad Pro had zero issues until yesterday as soon as I added the Sense watch all H.. broke lose. 

[Cynthiaq]

Fitbit version 3.39 on iPad iOS 14.4 is crashing back to Home Screen when my charge 4 is selected. 
Worked fine 2 days ago on March 1. 

[Jam2018]

I am on Charge 3 using an iPhone.  Yesterday it was freezing for me when I would try to look at the sleep details, however, if I left it there long enough it would eventually open the details.  Today when I just click on the view history screen, the app freezes and I have to close it and restart to look at anything else.  It is only a problem in regards to sleep data for me.  I am not a Premium member.

[thegreenheron]

Just chiming in to say upgrading from iOS 14.3 to 14.4 on the iPhone 11 did not fix the issue. 

[Jam2018]

It's not just iPad ... it's happening for me too on Charge 3 and iPhone.  Worked perfectly before the update to 3.39

[Jam2018]

It's happening to a lot of people on iPads and iPhones and it only started after the recent update to 3.39 ... I think for you it was just unfortunate timing that you were adding something new when this problem started to occur.  I was just about to switch to my new Charge 4 but think I will now wait till this matter is fixed ... if it gets fixed that is.

Update:

Exactly ... and agree!
Why is this forum thread marked as 'Solved' when it is anything but???

Moderator edit: subject for clarity 

[PaulaCWest]

Why are we not hearing anything from Fitbit? This is going on 5 days now...

[Jam2018]

Well I don't know what they've done behind the scenes but suddenly just now my sleep data is working correctly again on my Charge 3 / iPhone.  I clicked on the Sleep History and it took a second to open but opened the details right away once I was in there.  I closed the app and reopened it and the information was once again populated.  I don't know if it is just a momentary thing but as of this moment it seems to be working correctly once again for me.

[PaulaCWest]

Lucky! Mine is still crashing.

[SunsetRunner]

Ya it so should not be marked as solved but I think they want us to answer the questions so they can get it fixed and thats the way to get us to see it. I get 90 days free on premium but I’m so not going into that rabbit hole as its a endless $$ pit in the long run. Funny part is we are all on the same IOS for Apple and we all have different issues going on with the Fitbit app. My iphone 10 zero issues my iPad Pro only started with issues when I added the new watch last night. 

[Jam2018]

I don't know ... it is working now although a little bit slow but at least it is working and not freezing up the app, so perhaps they are working on things in the background.  Just the same I think I'll wait to switch to my new Fitbit till the issue is completely resolved.  Hopefully it's fixed for everyone soon.

[PaulaCWest]

Fingers crossed!

[SunsetRunner]

Ya this second I am starting to regret buying the fitbit sense as had no problems until last night and only with the sense on my iPad it crashes the app as soon as I try and go into its settings on my iPad. Our Fitbit scale Aria Air is semi ok it works on my iPad for going into settings but today it does not show BMI and it did everyday until today. So for me everything started last night as soon as I added the fitbit sense watch. I do know they had some kind of issue this AM and trying to get it fixed. I just want to use my iPad for the app as the phone is to small and annoying to use. I tried reinstalling app and the two fitbits nothing has worked on my end. 

[SunsetRunner]

So is mine your not alone and if its not a crashing app it’s missing information:/ 

[Kermit-The-Frog]

@LiliyaFitbit 

Great news!

For those who use an iPad.

But Apple uses a different OS for iPad than for iPhone.

Any updates for those of us who use the iOS (read: iPhone only) version?

Also, you mention that the team is hard at work on this issue. This begs 2 questions:

Question 1:  Within what time window can we expect a repaired update?  An hour? A day? A week? A month? A year?  Any information as to when to expect a fix would be greatly appreciated. A watched pot and all that.

Question 2:  I’ve been using a Fitbit device for over 4 years. I’ve noticed application hiccups before. None has come close to the disaster of 3.39 for iPhone. This appears to be a monumental screw up indicating that someone or some team was not working as hard or as smart as they could have.

Honest suggestion:  would Fitbit please resubmit the version immediately preceding 3.39 to the App Store? Please?

While I’m sure there are plenty of errors that 3.39 was intended to correct, it has made my device virtually useless. The previous version is (obviously) ready to go and has been more effectively tested than the current version.  

I don’t know how Apple processes app Update submissions. Perhaps there is a lengthy process that Apple needs to go through to approve the version that was the immediate predecessor?  This would solve the acute problem NOW while Fitbit works to put out a more carefully tested/vetted version to presumably do what 3.39 was supposed to do in the first place?

All of the above is meant quite sincerely and constructively.

Thank you for your consideration.

Edited: to clarify to whom I was responding and reframe my suggestion for an immediate solution.

[PaulaCWest]

Agree, I’ve used Fitbit for 5 years and never had a problem like this, nor had such a poor/no response when reporting a problem to a corporation. Apple Watch lookin’ pretty good right now.