Hi!
Tiny issue I noticed today after using the Web API for a couple of days. The browser shows the following message:
You can close this browser window
I make this mistake myself as a non-native speaker all the time but successful is written with two "s".
Answered! Go to the Best Answer.
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
Hi @holgerflick
I just went through the flow again and I don't see a message appearing after consent is made. I'm wondering if the application is populating this message, not Fitbit. What application are you using? If this is your own application, would you please private message me the full authorization URL?
Thanks!
Gordon
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
Hi @holgerflick
Thank you for reporting the typo. I'll be happy to work with engineering to get it fixed. Would you please provide me with the steps you took to reproduce the message? Right off the top of my head, I'm not familiar with it.
Thanks!
Gordon
Best AnswerThe message is shown after completing a login on the authorization page which can be accessed using the URL https://www.fitbit.com/oauth2/authorize
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
Hi @holgerflick
I just went through the flow again and I don't see a message appearing after consent is made. I'm wondering if the application is populating this message, not Fitbit. What application are you using? If this is your own application, would you please private message me the full authorization URL?
Thanks!
Gordon
You might be correct as the browser lists the callback URL. I will communicate with the component vendor of the OAUTH framework that I use to clear it up. Thanks for your help!
Best AnswerJust to confirm: The developer of my OAUTH SDK found the string and corrected the mistake. It was indeed on my side. Thank you for your help!
Best Answer