Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues connecting to Strava #24

Open
0x09AF opened this issue Aug 20, 2023 · 0 comments
Open

Issues connecting to Strava #24

0x09AF opened this issue Aug 20, 2023 · 0 comments

Comments

@0x09AF
Copy link

0x09AF commented Aug 20, 2023

I set up a new app in Strava and filled in user_id and secret in settings.ini but I have a hard time pulling Strava data. Docker logs show that the connection is indeed established, I can see API requests on Strava app's page, but Fitly doesn't display any info from Strava. Some of the logs:

fitly  | Unable to set attribute nickname on entity <Shoe id=g5815688 name='Whitin trail Barefoot'>
fitly  | Unable to set attribute retired on entity <Shoe id=g5815688 name='Whitin trail Barefoot' resource_state=2>
fitly  | Unable to set attribute converted_distance on entity <Shoe id=g5815688 name='Whitin trail Barefoot' resource_state=2>
fitly  | Strava connected
fitly  | 'NoneType' object has no attribute 'tokens'
fitly  | Spotify not connected
fitly  | Error in https://api.spotify.com/v1/me/top/tracks?time_range=medium_term&limit=10&offset=0:
fitly  | 401: Invalid access token

The app looks gorgeous on the screenshots, but when deployed the main page simply says "Provide oura credentials" and nothing else. I do not own oura, I just want Strava data.
I wonder if Strava has changed their API access rules since the last commit made to this app. Looking forward to using it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant