Refresh Token when Fitbit API is down

[AkisAkakis]

Hello all,

I have developed a .NET Core App that asks every once in a while data from my Fitbit account. All the authorization process is following the official guide

My App is trying to keep a stable communication with my Fitbit account but, when the Fitbit API encounters an error, the Refresh token becomes useless and my App stops. Without the input of the user the app wont start again since the refresh token is not authorized anymore.

The only way to resolve this is to open my App and re-grant access with my Fitbit account which creates a new Refresh Token.

Is there a way to bypass to ask the user to re-grant access, since he has already done that, and somehow create a new connection.

[Gordon-C]

Hi @AkisAkakis 

Would you please tell me what error your application receives when the refresh token becomes useless?   The refresh token should never expire but it can only be used once.   Are you able to refresh the user's access token at least once?   When you refresh the user's token, are you replacing the old access and refresh token with the new access and refresh token you receive?

Gordon