Obtain new refresh token

[mattyvau]

I previously set up the app successfully a while ago, with crontab based updates going fine since. I think my refresh token expired I was otherwise lost somehow as new activites weren't imported for a few days. My .env was missing the token when I looked.

Stats for Strava doesn't prompt me to connect to Strava like it did on initial setup.

How do I go about re-running that process for the proper refresh token (not the one on the API page)?

[robiningelbrecht]

Your refresh token should be valid forever, there's no need to refresh it

[mattyvau]

Sorry for the slow reply.

Strangely, my build seems to have stopped working. Maybe it was due to mixing Portainer and manual docker compose. I think the .env got messed up and now I don't have the proper token.

I'm currently using the refresh token obtainable on the API page, but if I recall correctly that wasn't what we needed to setup. Somewhere along the line my import-data stopped working. A manual run shows this:

Client error: `GET https://www.strava.com/api/v3/athlete/activities?page=1&  
  per_page=200` resulted in a `401 Unauthorized` response:                     
  {"message":"Authorization Error","errors":[{"resource":"AccessToken","field  
  ":"activity:read_permission","code":"missing" (truncated...) 

[robiningelbrecht]

Indeed, you need to remove the refresh token from your .env file and remove index.html from build/html/index.html
After that, if you navigate to the app, the authorization process should kick in and you can obtain a new refresh token