help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

The app shouldn't lose passwords between upgrades!

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎12-15-2017 00:42 - last edited on ‎12-16-2017 10:28 by Fitbit Moderator

‎12-15-2017 00:42 - last edited on ‎12-16-2017 10:28 by Fitbit Moderator

The app shouldn't lose passwords between upgrades! 

 

Whoever thouht this was a good idea should be fired, as should the manager who approved it and the director that signed off on it.

 

Moderator edit: Updated subject for clarity and format

 

Best Answer
0 Votes
2 REPLIES 2

‎12-15-2017 00:51

‎12-15-2017 00:51

I note you are using the iOS app. There has been a bug with this that's been causing people to have to logon more than was intended. I don't think it was a design decision as you suggest. Keep an eye on the following thread for the latest updates on that bug:

 

https://community.fitbit.com/t5/iOS-App/App-version-2-39-keeps-logging-out/td-p/2142070

Best Answer

‎08-30-2019 20:44

In response to SteveH

‎08-30-2019 20:44

if not a design decision, it's a QA issue.  Just a differemt set of folks to fire, that's all. Anyway, the issue seems to have been resolved long ago; perhaps test protocols were updated....

Best Answer
0 Votes