API problem; returns activity:read_permission

Did you make sure that you use exactly the access token that you got from the token refresh and not the token from the Strava API setup page or a token from another connected athlete?

Yes, I’m pretty sure
When I request manually using curl and only access_token, got the same error for that particular Athlete:
Request: 

curl -G -v GET "https://www.strava.com/api/v3/athlete/activities?after=1730415600&before=1764285275&page=1&per_page=10" -H "Authorization: Bearer [[access_token]]

Answer:

{"message":"Authorization Error","errors":[{"resource":"AccessToken","field":"activity:read_permission","code":"missing"}]}

But read_permission already granted. Revoking and adding permissions again doesn’t work

I think that might be problem with permissions

I’ve just tried again revoking access for app (removing it from settings page https://www.strava.com/settings/apps), an adding again and I’ve received error from strava: Error 403: Limit of connected athletes exceeded

Quotas should not be exceeded (I’ve made just few test requests today)

A minute later after refreshing strava.com, app returned spontaneously "just like that"

I’m still having the same errors {"message":"Authorization Error","errors":[{"resource":"Athlete","field":"access_token","code":"invalid"}]}

For revoking access it would be better to use the deauthorization endpoint described in https://developers.strava.com/docs/authentication/#deauthorization, it’s possible that revoking from the user side leads to a delayed update of the total number of currently connected athletes. The new error is not the same and probably reflects that the token can’t be used anymore because of the revoked access.

https://developers.strava.com/docs/authentication/#deauthorization -done that with: curl -v -X POST "https://www.strava.com/oauth/deauthorize" -H "Authorization: Bearer [[ "access_token" ]]
It worked with result {"access_token":”xxxxx”} and app dissapear from strava.com settings..

...but after a moment shows up again back. Refresh Token changed. I’ve updated data, and got refreshed token… and tried to connect again with the some error: {"message":"Authorization Error","errors":[{"resource":"Athlete","field":"access_token","code":"invalid"}]}