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: 

OAuth 2 access token issue

‎12-01-2015 19:59 - last edited on ‎12-01-2015 20:32 by

‎12-01-2015 19:59 - last edited on ‎12-01-2015 20:32 by

Hi, 

I got a problem in my own app while using oauth2.0.

 

Everything works fine on the first run, but after that if want to get my access token again. Chrome custom tabs will open and stay on an empty page and it won't properly redirect. 

 

Please advice. Many thanks...

 

Moderator edit: Moved this reply to its own topic.

Best Answer
Labels:
0 Votes
1 REPLY 1

‎12-01-2015 20:33

‎12-01-2015 20:33

Can you please clarify:

- Are you building an Android app?

- Are you using the OAuth 2.0 implicit grant flow?

- What is the URL when the Chrome tab opens? Does it change?

Best Answer
0 Votes