Error 400 when refreshing short lived tokens

[David Martínez]

Hi 

I'm receiving the following response when I try to refresh some short lived tokens: 

{"message":"Bad Request","errors":[{"resource":"RefreshToken","field":"refresh_token","code":"invalid"}]} 

All my tests are working well. Most users has no issues and the tokens are refreshed without problems except some random users (didn't detect any pattern).

I use the Strava webhooks, so if an user does not add any new activity in 2 weeks, the tokens will not be refreshed until the new activity received. 

This is my question: the refresh token has its own expiration? Must I refresh by hand the tokens of my users before other time limit? I know I must refresh the access token after 6 ours calling to https://www.strava.com/api/v3/oauth/token with the last refresh token for the user but I checked that a refresh call with a 10-day-old user refresh token doesnt works, giving me the specified error.

Thanks

Thanks

[Nick Pedersen]

Hey David,

We're seeing the same issue. For a very small subset of users we're getting a 400 response from the API request to refresh a token. We've prompted the user to disconnect and reconnect Strava and the issue is still occurring. In our case we asked them to reconnect and perform an activity which happened within a 10 day window and they still received the same error, so I'm not as convinced that the refresh token expiring is the issue.

Any chance you got to the bottom of this?

Cheers,

Nick

[Alex VanLaningham]

We just started seeing this issue yesterday as well at trainerday.  So far only 2 users have been affected.