Repository navigation
Check the Strava scopes the athlete granted; 1.15.4 - #83
Draft
sturimcode wants to merge 1 commit into
Draft
sturimcode wants to merge 1 commit into
sturimcode wants to merge 1 commit into
Conversation
Strava's changelog (2026-04-23) says the token response now lists the granted scopes. The athlete can untick profile:write on the consent screen, which used to surface only later as an ambiguous 403. - Setup refuses a grant without profile:write and says how to fix it. - Granted scopes are saved with the tokens and kept across refreshes. - doctor and weight-update 403s name the missing permission when the scopes are known; older grants without a scope list behave as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PbMTbkp1w5JTQYmxMm2n6Q
Owner
Author
|
The Re-running that job when a macOS 3.15 runner is available should turn Generated by Claude Code |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Strava's API changelog entry for 2026-04-23 says the token response now has a
scopefield. It lists the scopes the athlete actually granted, separated by spaces. On Strava's consent screen the athlete can untick individual permissions. If they untick profile editing, eufy-sync used to save the grant anyway, and every later weight update failed with an HTTP 403. That 403 message mostly pointed at the API app's subscription.What changes
scopequery parameter. Ifprofile:writeis missing, setup stops without saving the tokens and says to run--setup-stravaagain with that permission left ticked.scopereturned by Strava replaces the saved list; otherwise the saved list is kept.check_connection: reports a known grant withoutprofile:writeand offers--setup-stravaas the fix.update_weight403: when the scopes are known, the message names one cause: either the missing permission or the subscription. Grants saved before this change have no scope list and get the same combined message as before.profile:write,profile:read_all) are unchanged.Testing
pytest: 803 passed, 6 skipped.ruff checkis clean. The new tests cover setup end to end through the local callback server, with the browser and the token exchange mocked. They also cover how scopes are kept across a refresh and the new error messages.Generated by Claude Code