08-15-2017
11:35
- last edited on
01-31-2018
14:08
by
KateFitbit
08-15-2017
11:35
- last edited on
01-31-2018
14:08
by
KateFitbit
Fitbit update: 1/31/2018: After several mitigating fixes, this issue has been resolved in the recent update 2.45. Please update your app if you are experiencing this. We know there were a few that continued to experience this issue, thank you for you for your reports and patience. We will be closing this thread for further comments. If you are still being logged out after updating your app, please start a new thread and we will open a new investigation.
Fitbit update: 12/19/2017: Hi Everyone, with the release of iOS app version 2.44.1, the log-in issues have been addressed. Please update your app. If you are still experiencing this issue after the update, please let me know how often this is occurring and if you are seeing any other error message and I will review with our team.
Fitbit update: 11/21/2017: It appears that some users on 2.43 are still experiencing having to log in continuously. Our team has been alerted and I'll continue to update this thread.
Fitbit update: 11/21/2017: This issue is currently resolved. If you are still having to log in multiple times, please ensure you have updated your app to version 2.43.
Fitbit update 11/15/2017: Hi Everyone - there have been some mitigating fixes, but the issue does not appear to be entirely resolved at this time and our team is still working on this. Thanks again for your patience, we know this has been an ongoing issue and hope to have it fully resolved soon.
Fitbit update 10/31/2017: Our team continues to work on the issue of users being logged out of their app. While there have been some mitigating fixes in previous updates, we are aware that this issue is not resolved for all. I will continue to update thread. Thanks very much for your patience.
Fitbit update 9/30/2017: some mitigating issues have been resolved in the latest update, however, we are aware the issue has not been resolved for all. Please update your app if you haven't already done so.
Fitbit update 9/12/2017: Our engineers have implemented some mitigating fixes that should help some with this issue in version 2.40, however, some people may still be experiencing this and our team is continuing to review. We truly appreciate your patience.
Fitbit Update 8/24/2017: Hi Everyone - Thanks again for reporting this issue. Our team is still reviewing. I'll be updating this thread once we learn more, your patience is truly appreciated.
Hi everyone! Thanks for reporting this login issue with the last iOS update version 2.39. I have brought this up to our team for further investigation. Thanks for your patience while we work on a fix.
Want to get more steps? Visit Get Moving in the Health & Wellness Discussion Forum.
Answered! Go to the Best Answer.
10-10-2017 19:16
10-10-2017 19:16
Help. It’s every day and it's only happened to me SINCE I updated to 2.41. This is a royal pain in the proverbial...
10-10-2017 19:42
10-10-2017 19:42
It took me 5 tries to finally get my watch to connect to the app today. I am about to sell it and buy an Apple Watch.
10-11-2017 05:27
10-11-2017 05:27
My phone is also making me log in to the app every single morning. What is odd is that my iPad, which has the identical iOS and version of the app, isn't doing that at all. Why would it be a problem on one device and not the other?
10-11-2017 05:42
10-11-2017 05:42
10-11-2017 06:22
10-11-2017 06:22
This is my third post on the subject, following posts on Oct 5 and Oct. 7. Sometime within the last 12-24hrs, the app logged me out.
10-11-2017 16:00
10-11-2017 16:00
Do you really think that if this much time passes before you can find a fix for this problem that anyone is going to trust the Ionic enough to buy one?
I know I won’t be buying one.
10-11-2017 22:56
10-11-2017 22:56
I have the Fitbit blaze. Last two days I have been unable to log into my app on my iPhone 6. I have restarted my phone and I have lots of storage. Also note my app is up to date. I cannot reset my account with a new password nor can I set up as a new account as it recognizes my email address. Need this fixed. I get my texts etc and I missing my notifications! Help please ASAP!!
10-11-2017 23:42
10-11-2017 23:42
This is still a problem for me. iOS 11 and the latest version of the app. It’s incredibly annoying...
10-12-2017 00:39
10-12-2017 00:39
It is the latest update that has caused this for me in the last week. I have an iPhone that is fully updated for iOS and Fitbit app.
10-12-2017 05:27
10-12-2017 05:27
And something else new that the app is doing:
Upon being forced to log back in, the app crashes. When I restart the app, it updates the database.
If, after all these clues, you don’t have anyone excitedly exclaiming, “Ooo, I know right where to look!” you don’t have the right person on staff yet. You need one of those.
10-12-2017 08:28
10-12-2017 08:28
Deleting and reinstalling the app seems to have fixed the problem for me.
10-12-2017 09:42
10-12-2017 09:42
@dougcornelius wrote:Deleting and reinstalling the app seems to have fixed the problem for me.
Did you experience any unintended consequences? Any data loss?
Thanks in advance.
10-12-2017 12:25
10-12-2017 12:25
eye95 I too deleted and reinstalled the app and it seems to have fixed the problem. No I did not lose data. I will say I have long had conflicts re: bluetooth on my ipad (air2) versus my iphone 5s, so I have elected not to activate bluetooth for my two devices on ipad for now. My iphone is running IOS10 as I usually wait a month or two after a new IOS release before installing in case there are issues.
Good luck
10-12-2017 14:20
10-12-2017 14:20
Thank you.
More observations for the developers:
I started an exercise today. The watch showed full green bars of connectivity to the iPad. Sometime during the exercise, connectivity was completely lost. I discovered this fact when I saw an icon on the watch showing a red phone with a slash through it.
Trying to open the app, I had to log in again. (I logged in this morning.) Once again, the app announced it was updating the database. That is one of the reasons I am concerned about deleting and reinstalling the app: I worry about how well the database is maintaining my data.
Is anyone at Fitbit listening? No one has replied in a while.
10-12-2017 18:31
10-12-2017 18:31
I deleted the app and reinstalled. When I set up as new it already recognizes my email address. When I login with my existing email address it doesn’t process.
I might need to create a new email address just for my “dumb” smart watch!! Guaranteed all my info will gone forever. All those wasted steps...😑
10-12-2017 19:02
10-12-2017 19:02
still the same problem. always logout.
and more, always crash. then I mush launch the app again.
Its been almost 2 months. and there has no resolution?
10-12-2017 19:15
10-12-2017 19:15
Dear,
Seems that the losing login credentials after relaunching the app, is keeping Fitbit development team busy for a while!
The formal responses aren’t really comforting!
Can we have a clear and committed answer from the team on when this issue will be resolved? I’m sure that this isn’t a great selling point. Also I’ve seen that the battery lifetime of my blaze is reduced too. Please an appropriate and firm answer is more than welcomed. Thanks.
10-12-2017 19:42
10-12-2017 19:42
It's been happening to me too. Newest update but still having to log in every time I want to see my progress and my challenges. I know, first world problem, but it's frustrating that no other app does this except for one that I have a lot of money invested in with the watch.
10-12-2017 19:47
10-12-2017 19:47
I solved my problem with the app logging me out. I deleted it from my phone and reinstalled it. All is working now. So, it seems like just updating the app did not remove some coding that caused this problem.
10-12-2017 22:30
10-12-2017 22:30
Same issue for me on iOS, I can log back in, however. Just random log outs. I've tried deleting the app, rebooting my phone, nothing helps.
In addition, I keep having GPS disconnection to my Fitbit Charge 2 mid-ride making having the fit bit almost useless. Please fix this.