App version 2.39+ keeps logging out

[AlessFitbit]

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.

[alienbeing]

Also still having this problem - iPhone 8, iOS 11.1, version 2.42

Thanks!

[crisiy]

So it worked all day until now 😞 Seriously frustrating. I have an iphone 6 my husband has a iPhone 7 we both have blazes and his app works fine while mine keeps logging me out! My friend has an iphone 6 plus and a blaze and her app is still fine. What phone is everyone using?

[Mathpup]

I have a 6, not updated to iOS 11 and a Charge 2.  I had one day last weekend when the app started right up, and I got all excited that it was fixed .... but not so much.  I've had to log in each morning since.  It's just plain annoying.

[beacon126]

iPhone 6, iOS 10.3.3, Fitbit 2.42 is logging me out. I was not having this issue before this version of Fitbit.

[Chris92057]

Not happy at all with the constant logging out of the Fitbit application on the iPhone and/or iPad. I can use the app on the device. Go back five minutes later, and be logged out. 

[RefRon]

I have an iPhone 5S iOS 11.03. I'm believing that the issues started
about the time I updated to iOS 11. Several other apps had to release
updates to coincide with iOS 11.

[NorthAgain]

Yes Anouther problem with the fit bit app, I have lost track of the number of bugs in the watch and the app since I got them, I will not be getting another fit bit after this one will look for something else

[mreso]

The fitbit app continues to log me out every couple days. Its been 3 months since this thread was started. Where is the fix?

iPhone 7, ios 10.3.3, fitbit app 2.42 (726)

[nickw444]

Looks like I spoke too soon, my app became logged out yesterday, so fully unpairing and re-pairing the device does not solve the issue.

[Danielnotsofar]

Most new apps link the phone to the account and allow us to login simply via touch..  Why do we even NEED to login more than once?

[Seth2207]

It says my version is 2.42 and I have to log in every time. It's a pain in the butt please fix!!

[KateFitbit]

Thanks again for your reports, it is appreciated. I'm hoping to have a complete resolution soon and will continue to update this thread. Have a great weekend. 

[momice]

I have the latest version of the app on both my iPhone and iPad and it randomly logs out on each one. Hope this is fixed soon. 

[lytefall]

A fix can’t come soon enough. It’s just about time where i am about to consider a new device and this is starting to make me consider other options.i have been pretty happy with Fitbit so far but this is testing my patience. 

[Gizzys25]

How much longer do we need to wait. 

Its getting frustrating having to constantly log in everytime I want to check my progress 

[SunsetRunner]

As frustrating as it is to continue waiting for the fix, I understand there can be complexities or other concerns that need to be addressed.

But, because of how long this problem has been occurring, could we at least get an update as to what the problem is? It appears to be an app problem when connectivity is degraded, or possibly a login token refresh problem.

At least some high-level information on the root cause would be helpful. The continued “we’re working on it” isn’t cutting it any more.

[Arlenedmoore]

Beyond annoyed with having to continuously login on my phone while trying to see my progress 

[AnnemieB]

Hello, Annemie from Belgium here : up till now this problem still occurs from time to time (not every time but still pretty often)

waiting for Fitbit to fix this ...

[SarahHall16]

My app is still logging me out all the time which is incredibly frustrating. 

I note that the Fitbit team have been working on this issue since May 2017. Given 7 months have now passed, perhaps there will be a definitive timeframe by which this issue will be finally fixed?

[honglong1976]

Agreed! 7 months is quite long.

Do they only have 1 programmer?