09-16-2024 09:30 - edited 09-16-2024 10:10
09-16-2024 09:30 - edited 09-16-2024 10:10
Dear Fitbit community,
since today around 14:03 UTC our systems are responding with a 403 response for all our users during our refresh token implementation. The content of the response is "error code: 1010".
This is happening for several different Fitbit Apps (with different ClientIDs) on our side.
We did not change anything on our application side, this started to happen out of a sudden.
Was there any update performed that might have done any impact?
I cannot find anything in particular regarding "error code: 1010".
Any help appreciated
Best
Answered! Go to the Best Answer.
09-17-2024 07:42
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.
09-17-2024 07:42
Would you please confirm the time frame that you received the errors and if you are still seeing the problem?
Thanks!
Best Answer09-16-2024 12:15
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.
09-16-2024 12:15
Thank you, @threif
We are looking into it.
Best Answer09-17-2024 01:32
09-17-2024 07:42
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.
09-17-2024 07:59
09-17-2024 07:59
Hello,
thank you very much. I can confirm that the issue is now resolved since today around 9:45 UTC.
Best