iOS Fitbit app constantly crashes with iOS 13 beta

[dmfresco]

I updated my iPhone XS to iOS 13 Beta 3 and now the iOS Fitbit v2.95 constantly crashes.  I have tried to delete and reinstall it several times to no avail.  Any ideas to get it working again or get a patch for iOS 13?

Moderator edit: updated subject for clarity

[LizzyFitbit]

Hi @dmfresco, @Missyrmdlm and @TKCMuzzer. I'm glad to see you here again.

@TKCMuzzer, I appreciate your insight. @dmfresco and @Missyrmdlm, thanks for taking the time to share your thoughts, and I'm sorry that you're having this situation. As mentioned above, Fitbit has received feedback from users that have this issue when the iOS 13 beta version. This version isn't yet supported for the Fitbit app. But our team will keep working on the Fitbit app, so it can work flawlessly with your phones when updating to iOS 13.

See you around.

[DokteurP]

 @LizzyFitbit an ETA for a resolution would be great! Since I bought my FitBit I end up with frustration: SPO2 never officially implemented, not even Apple Health App support... and now iOS 13...

What can I do to get a full refund and return it?

[Lorenkwatson]

If you are within your return period with the retailer you purchased through, you can do it that way. If not, then you can not return it. 

[dmfresco]

@LizzyFitbit Thanks for your reply, I truly feel you are missing the point.  We all know that iOS 13 Beta is just that beta software and it will have issues with other software, such as Fitbit.  No one here is saying that Fitbit is in the wrong for using the fact that iOS 13 Beta as an excuse for Fitbit not working. As I read the over 100 posts in this thread, the primary sentiment is disappointment that Fitbit seems flatfooted and not stepping up (pun intended) to fix this issue, and get ahead of this bug in advance of the formal release of iOS 13, which is only weeks away.  And if you are the person who marked this thread as SOLVED, then I cannot disagree with you more!  There is nothing solved about it, just explanations and apologies, but little in the way of action from the software development and engineering facets of Fitbit.

Moderator edit: word choice

[Benjr77]

The new ios13 Beta 4 out today is totally compatible with the Fitbit App. It looks as though Apple have fixed the bug. What a relief!

[dmfresco]

I am updating my iPhone right now to Public Beta 4.  So fingers crossed!  However, if the time server issue is the true problem, and as last week things stopped working on Sundays, this new iOS release working with Fitbit is just a coincidence.  I am not going back to iOS 12 just for Fitbit.  So here's hoping that Apple changed something or Fitbit will finally make a conspicuous effort to get us all up to speed on iOS 13 Beta. 

[dmfresco]

So far, so good with Public Beta 4

[thesidj]

Unable to sync. Have to change to date and then sync. What version of the app are you on? I am on Fitbit 3.2 (851) and on iOS Public Beta 4 🙄

[dmfresco]

Fitbit 3.2, not sure how to check the build.  iOS 13 Public Beta 4 (17A5547d).  Still working as of today.

[DokteurP]

@thesidj I'm on iOS Public Beta 4 with Fitbit 3.2 (851) as well (@dmfresco check built under Account/Help) and everything works fine... yet... and I'm EST timezone (GMT-4) if this is relevant!

I'm using an iPhone XR

[dmfresco]

It's Thursday morning EDT and Fitbit 3.2, build 851 continues to work on iOS 13 Public Beta 4.  Progress‽‽‽‽‽ 

[Marina_EatFit]

Mine is CRASHING. I wish I could return the device and get another one as tracking heart rate is essential for my training for an event. Sad. 

[dmfresco]

@Marina_EatFit Some people on this thread, including me, succeeded in getting it to work by advancing the date of their iPhone to next Sunday, launching Fitbit, and then restoring their iPhone to the correct day and time.  That worked on my iPhone. My iPad running iPadOS 13 Beta started working again by itself last Sunday.  My hunch is there is something to this date issue but it's quirky.  Give the date trick a try.  You will know immediately if it works or not. Fingers crossed

[killer2239]

Then go back to iOS 12? When you run a beta OS you risk apps not working.
That is why it's a beta and you have to enroll in it. I get it's a stupid
issue to have and Fitbit should fix it but you can't really complain about
wishing you could return it if you chose to install the beta to use on your primary daily device.

[thesidj]

The build works okay, but I have to change the date to a future one in order to sync. 

[LizzyFitbit]

Hi everyone. I'm glad to see all of you here, and I'm sorry for my delayed response. 

I understand how you're feeling, and I'm sorry that you're going through this. We provide support to the latest stable version of iOS which is 12.4. At this moment we don't provide full support to preview or beta versions of your iOS device since this isn't the official version. While there isn't a time frame when this will be resolved, our team will improve the Fitbit app so it can work with iOS 13 once it has been fully released to the public.

@Lorenkwatson, thanks for your great help. @DokteurP, @Benjr77 and @thesidj, thank you also for sharing the steps that you've tried.

@dmfresco, about your other inquiry please take in mind that since this is a public forum, and other users experiencing this situation could have found my post helpful enough to mark it as accepted solution. I see your point of view, and as mentioned before, Fitbit is receiving feedback from the Community and they're working on this.

See you around.

[Missyrmdlm]

The app has been running fine for me for a week. Currently of iOS 13, dev 5. And it fixed itself, it was clear no practical user intervention would get it to go. I used alternative syncing on stable jb iOS 9.3.3 when the app was down. 

[Marina_EatFit]

I do not recall asking for your opinion.

[Mechelle1213]

Whoaaaa super harsh for a forum smh

[SunsetRunner]

Calm down. You're writing in a community board, of course someone will reply to your post and state their opinion. If you don't like this aspect then please re-evaluate why you're here. :3

In general this board is quite toxic. Yes, having problems with a device sucks but that's no reason to get harsh. If for example someone uses iOS 13 BETA and can't sync their tracker with the app anymore then it's their own fault for using a beta version of iOS 13. It's totally normal that apps might not work properly (the beta of iOS 12 back then killed a lot of apps for me) but that's something that comes with a beta. No one can fault a developer for taking their time to update their apps. That's why Apple releases the developer-betas in summer and releases the finished update in fall. Updating an app and making sure that everything works with the new version of an OS takes time. If that's enough reason for some to instantly switch to an Apple Watch, maybe the Fitbit wasn't the right device to begin with or you might have a problem. 

If you want your apps to always work properly, don't use a beta! Or revert back to the last stable version of iOS (which is pretty simple). 😉