If `FASTLANE_SESSION` is invalid or missing xodes commands should fail when using `--use-fastlane-auth`
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 4.8k
- Forks
- 182
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 1
Description
IMHO if FASTLANE_SESSION is invalid or missing xcodes install --use-fastlane-auth should fail fail early as opposed to falling back to Apple ID login.
xcodes install 16.3 --use-fastlane-auth
FASTLANE_SESSION not set
Apple ID:
I would argue this is not only more predictable behaviour but it's also more CI friendly as invalid session tokens can cause a CI pipeline to simply freeze indefinitely waiting for user interaction.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the xcodes install command path and trace how --use-fastlane-auth handles a missing or invalid FASTLANE_SESSION. Reproduce the command shown in the issue, then verify that authentication fails before prompting for Apple ID login when the session is unavailable or invalid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100