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: 

Will we get refresh tokens that do not expire?

‎04-15-2016 17:07

‎04-15-2016 17:07

If anything happens inbetween making the call to the Fitbit API to refresh the token and saving it to the database then that user's refresh token is lost forever and they will notice Fitbit not working with our app anymore. Clients simply cannot guarentee that this will never happen. I am wondering if you guys are looking into an implementation where the refresh token is permenant? 

 

Thanks 

Best Answer
Labels:
0 REPLIES 0