FitbitLoginStat.build.<asynchronous suspension

[AshBreeze]

But I am still stuck in this page, no matter how I press the "Allow" button, the page cannot be redirected even it is already granted by the other Fitbit watch user, who can find the application in their account. So I think it should be the Fitbit authorization issue of 

OAuth 2.0: Authorization URI

https://www.fitbit.com/oauth2/authorize . 

Any suggestion definitely welcome, many thanks

[AshBreeze]

---

@AshBreeze wrote:

But I am still stuck in this page, no matter how I press the "Allow" button, the page cannot be redirected even it is already granted by the other Fitbit watch user, who can find the application in their account. So I think it should be the Fitbit authorization issue of 

OAuth 2.0: Authorization URI

https://www.fitbit.com/oauth2/authorize . 

Any suggestion definitely welcome, many thanks

---

I also got the error message like this, 

{"errors":[{"errorType":"invalid_client","message":"Invalid authorization header format. The header was not recognized to be a valid header for any of known implementations or a client_id was not specified in case of a public client Received header = null. Visit https://dev.fitbit.com/docs/oauth2 for more information on the Fitbit Web API authorization process."}],"success":false}

[Gordon-C]

Hi @AshBreeze 

If you are seeing the error "Invalid authorization header format" when pressing the Allow button, I've seen this error when the client ID is not provided in the authorization URL.   See https://dev.fitbit.com/build/reference/web-api/authorization/authorize/.   Please double-check your authorization URL is correct.   If it is, please post it in this post so I can try it myself.

Thanks!

Gordon

[AshBreeze]

The url is correct.