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

[Marina_EatFit]

Someone here already helped me with the issue and that person is fantastic.
So I was surprised to see some random person attacking me for no reason
just because I was upset. This is a product , And the forum is about it. No
need to jump on me and tell me that I live my life wrong. There is Facebook
for that.
I appreciate your message. Thank you.

[SunsetRunner]

That's true. This thread helped me too and I'm glad we have some awesome people in this community.  I was just a bit angry about some people who say things like "Fitbit is stupid because they take their time to make their app compatible with iOS 13". As long as they manage to make it fully compatible until the release of iOS 13 in September everything is fine. If the Fitbit App doesn't workt after the release of iOS 13 then we can get angry. 

[dmfresco]

@SunsetRunner I don't recall seeing a single person aside from you type the word stupid in this thread. Perhaps you are pointing a finger at me?  The only point I was trying to make is the complete lack of any conspicuous efforts on the part of Fitbit to keep up with iOS 13 Betas. Speaking only for myself, I understand the perils and challenges of beta software and make allowances and offer patiences as software developers such as Fitbit work to catch up--truly! My frustration lies in the lack of communication and transparency in acknowledging the bug and no communication for WHEN they hope to a version that works with iOS 13 of any flavor.  We are weeks away from the official release of iOS 13 and the lack of any guidance other than don't play with beta software is not that inspiring. And @Marina_EatFit allow me to totally validate your upset.  It is not misplaced and I do not feel as though you expressed yourself in a non-friendly way, one bit. 

[SunsetRunner]

@dmfresco My quote was an exaggeration. You're right, no one wrote "stupid" but after reading through all six pages of this thread in on sitting (to find help) I was just left with a lot of negativity. But since everybody interprets words differently I guess that one is on me. ^^

And no, I wasn't pointing with my finger at you. You're one of the awesome members of this community I was referring to in my last post. 🙂

My only problem was that it seemed to me that some users are expecting apps to run flawlessly even when using a beta. You're frustration with the transparency of the development team on the other hand is totally valid. If multiple users are reporting a big bug like the one we were/are experiencing then there should be an official statement from them. It's always important to let the users know what the problem is and when it will get fixed. I guess the mods here can't do very much about it (other than reporting the problem to the development team) but that's not really an excuse for the lack of transparency on Fitbit's side. 

P.S: Is anyone experiencing the bug under iOS 13 public beta 4? 

[thesidj]

This is to confirm that the app is working fine with public beta 4 now 

[SunsetRunner]

@dmfresco My quote was an exaggeration. You're right, no one wrote "stupid" but after reading through all six pages of this thread in on sitting (to find help) I was just left with a lot of negativity. But since everybody interprets words differently I guess that one is on me. ^^

And no, I wasn't pointing with my finger at you. You're one of the awesome members of this community I was referring to in my last post. 🙂

My only problem was that it seemed to me that some users are expecting apps to run flawlessly even when using a beta. You're frustration with the transparency of the development team on the other hand is totally valid. If multiple users are reporting a big bug like the one we were/are experiencing then there should be an official statement from them. It's always important to let the users know what the problem is and when it will get fixed. I guess the mods here can't do very much about it (other than reporting the problem to the development team) but that's not really an excuse for the lack of transparency on Fitbit's side. 

P.S: Is anyone experiencing the bug under iOS 13 public beta 4? For me it runs perfectly — at least for now. xD

[LizzyFitbit]

Hi @Missyrmdlm, @Marina_EatFit, @Mechelle1213, @SunsetRunner, @dmfresco and @thesidj. It's always great to see you here. I'm sorry for the delay in my response.

Thanks for the information that you've provided, as well for sharing your feedback. I understand your point of view about this situation and our team will continue working to improve the Fitbit app so it can work with iOS 13 once it's fully released to the public.

We want our Fitbit Community to be a place where users can come to share their feedback and stories in a positive and conducive manner, so please keep in mind the Community Guidelines when posting. Your opinions are always welcome.

Hope to see you around.