Skip to content

Fastlane initial setup - #459

Merged
bradleymackey merged 36 commits into
mainfrom
release/fastlane-setup
Oct 21, 2025
Merged

bradleymackey merged 36 commits into
mainfrom
release/fastlane-setup

Conversation

@bradleymackey

Copy link
Copy Markdown
Member
  • Create fastlane metadata
  • Ensure build completes with fastlane
  • Not uploading yet due to internal failures, but we will fix those in short order

@bradleymackey
bradleymackey merged commit 090aea4 into main Oct 21, 2025
1 check passed
@bradleymackey
bradleymackey deleted the release/fastlane-setup branch October 21, 2025 10:04
bradleymackey added a commit that referenced this pull request Sep 25, 2026
## Summary

`ios release` asked for the Apple ID username four times per run: once
for `get_certificates` and once for each of the three
`get_provisioning_profile` calls. `fastlane/Appfile` is gitignored
(since #459), so those actions had no default, while
`latest_testflight_build_number` and `upload_to_app_store` already
passed `username:` explicitly.

This passes `username:` to the signing steps the same way, and gives the
`upload` lane the same `username:`/`team_id:` as the release lane's
upload so it doesn't prompt either. The existing `.gitignore` for
`Appfile` is left in place.

The Apple ID password and 2FA are still needed interactively (or from
fastlane's saved session), so `ios release` still has to run from a
terminal.

## Verification

- `bundle exec ruby -c fastlane/Fastfile` → `Syntax OK`
- `bundle exec fastlane lanes` → all four lanes list
- `make validate` for the `Validate (local)` status

No lane was executed; the next `ios release` run exercises it.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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

Successfully merging this pull request may close these issues.

1 participant