Closed (fixed)
Project:
Strava API
Version:
3.0.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
15 Jul 2026 at 11:36 UTC
Updated:
29 Jul 2026 at 18:45 UTC
Jump to comment: Most recent
Follow up from #3007441: Use new authentication and scope
Leftover email-based code (UserManager::getUserByEmail(), userExists()) and outdated scope docs should be removed.
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
markconroy commentedComment #4
f0ns commentedComment #7
f0ns commentedCleaned up this code.
Comment #9
f0ns commentedThe MR (targeting 3.0.x) removes all leftover email-based code that stopped working when Strava's OAuth dropped access to the athlete's email address (#3007441):
UserManager::getUserByEmail()andAthleteUserHandler::userExists(): no remaining callers.AthleteUserHandler::userCreate(),UserManager::registerUser()and its helpers (unique username generation, user picture download, registration checks). Their only caller was already commented out.strava.user_managerservice dependencies and thedrupal:filedependency, which only existed for the user picture download.public,write,view_private) inStrava.php.Note for the release notes: this removes public methods, so custom code calling them will break (acceptable while 3.0.x is in alpha).
Follow-up needed
While verifying the removals I found a pre-existing gap (not caused by this MR): when a logged-in user authorizes Strava for the first time,
AthleteUserHandler::connect()never creates the athlete entity: that branch has been commented out since #3007441. Creating a Drupal user for anonymous visitors is genuinely blocked by the missing email, but creating an athlete entity for an already-authenticated user needs no email:AthleteManager::createAthlete()still exists and has everything it needs. This deserves a follow-up issue to wire that up so first-time linking works end to end.Comment #10
f0ns commentedCreated separate issue for the follow-up.