OAuth 2.0 Fitbit Authorization suddenly giving bad request (400) error

[SAllen0400]

Hey guys, 

My iOS app had been authorizing Fitbit users seemlessly starting in September 2015. We are using OAuth 2.0 and are Intra-Day Time Series approved.

Around April 9th, new users started reporting an error when they tried authroize their Fitbit accounts. We are getting a Response Code 1011 - Request Failed: bad request (400) when users click the "Allow" button after they've entered their email/password.

Does anyone have any ideas on why this would have been working fine for 7 months, and then suddenly not work anymore (we haven't updated the app or changed the code).  

Could our Intra-Day Time Series permissions have been revoked for some reason?

Any help is appreciated.  Thanks!

Sean

[JeremiahFitbit · Accepted solution]

What is the URL in the address bar where you see this error?

Fitbit redirects people back to your app when they click Deny/Allow. If the error you see is on your URL, this is a problem with your app.

[SAllen0400]

Thanks for the response, Jeremiah. Digging deeper into the URL we found our issue and have submitted our bug fix to Apple. 

Thanks!