06-08-2016 00:09
06-08-2016 00:09
I hope someone might be able to help point me in the right direction for sporadic issues we're having with refresh tokens in our app:
GuzzleHttp\Exception\ClientException: Client error: `POST https://api.fitbit.com/oauth2/token` resulted in a `400 Bad Request` response: {"errors":[{"errorType":"invalid_grant","message":"Refresh token invalid
Of the 100+ users that have connected to Fitbit, only 10 have so far experienced this issue, but i'm finding it impossible to tell if those users have revoked the access token on their end, or if something else if happening that might keep affecting more and more users.
Our logic is as follows:
As far as I can see, the code and logic is as intended, and tests with my own Fitbit account work fine.
Any advice would be greatly appreciated. I've emailed Fitbit but have not heard back at all.
07-12-2017 10:01
07-12-2017 10:01
I am getting this same issue. Did you find any solution for that?
07-21-2017 09:30
07-21-2017 09:30
We're having major refresh token invalid issues over here. Can someone please take a look at this?