~ knotless Search/
↑↓ move↵ open⇧↵ all results

geesawra.industries/old-fella

Old people's social media app

0
1
main
64 lines · 7.4 KB Raw History

Xcode Cloud

Knotless is the source repository. Its xcode-cloud workflow copies main and version tags to a private GitHub mirror. A mirror is a copy of a Git repository. Xcode Cloud reads the mirror because Apple supports GitHub as a source provider. Apple’s supported source providers

The Knotless check reports whether GitHub accepted the push. Build status and logs appear in Xcode Cloud. Xcode Cloud uses GitHub events to start release builds. This setup needs no App Store Connect API key. Apple’s start conditions

Set up the mirror

The workflow targets geesawra/old-fella-mirror on GitHub. It runs on Knotless runner did:plc:4bocpkn5zkwe4wuu4plrj5kt. The GITHUB_MIRROR_KEY secret holds the private half of a pair of SSH keys.

  1. In the GitHub mirror, give its deploy key write access. A deploy key gives access to one repository.
  2. In Knotless, grant GITHUB_MIRROR_KEY to the named runner for refs/heads/main, refs/tags/testflight/v*, and refs/tags/v*. Use the private key as the secret value.
  3. Push the workflow to main on Knotless. Make sure that the xcode-cloud check succeeds and the mirror shows the same commit.

GitHub deploy keys · Knotless workflow secrets

Connect the Apple Developer team

  1. In project.yml, make sure that DEVELOPMENT_TEAM matches your paid Apple Developer team. If it changes, run xcodegen generate and push the change and regenerated project to Knotless.
  2. Register industries.geesawra.oldfella and industries.geesawra.oldfella.share on that team. Register group.industries.geesawra.oldfella and assign it to both identifiers.
  3. Clone the GitHub mirror into a separate directory. Open the checked-in OldFella.xcodeproj from that clone so Xcode detects GitHub.
  4. In Xcode, add your Apple account. Open Report navigator → Cloud → Get Started and select Old Fella and the paid team.
  5. Grant the Xcode Cloud GitHub app access to old-fella-mirror when Apple asks. Select the App Store Connect record for industries.geesawra.oldfella or create it during setup.
  6. Set the first workflow to use the OldFella scheme and an Xcode version with the iOS 27 SDK or later. Choose a Manual Start condition for main and a Build action for iOS. Remove the default start conditions and Archive action.
  7. Start the first build on main. If Xcode generates OldFella.xcodeproj/xcshareddata/xcodecloud/manifest.json, add it to the Knotless checkout and push it to main.

Apple’s App ID setup · Apple’s App Groups setup · Xcode Cloud setup · Connecting Xcode Cloud to GitHub

Send a build to TestFlight

After the first build succeeds, create an internal tester group in App Store Connect under TestFlight. Add yourself as a tester. Apple’s internal testing guide

In Xcode Cloud, create a workflow named TestFlight. Use the same project, scheme, and Xcode version as the first build. Under Start Conditions, add Tag Changes and choose Tags beginning with testflight/v. Remove the default Branch Changes condition. Add an iOS Archive action with Deployment Preparation set to TestFlight (Internal Testing Only). Add a TestFlight Internal Testing post-action and select your tester group. Apple’s distribution workflow guide

Run just install-deps to install Go and the pinned version of AutoTag. Push main to Knotless and wait for the mirror check to pass. From the Knotless checkout, run just testflight to push a tag such as testflight/v0.1.0-beta.1. Xcode Cloud sends the build to your internal tester group. AutoTag

The app and Share extension use version 0.1.0 and the build number from Xcode Cloud. What to Test lists commit subjects since the previous TestFlight tag. The first TestFlight build uses the history up to its tag. Long notes show the newest entries that fit. Apple’s TestFlight notes guide

Schedule TestFlight builds

In the private GitHub mirror, add KNOTLESS_HANDLE as an Actions variable. Save a Knotless app password as KNOTLESS_APP_PASSWORD in Actions secrets. Use an account that can create tags in the Old Fella repository. GitHub Actions secrets

After the workflow reaches the mirror, open Actions → Nightly TestFlight. Click Run workflow on main. The job waits for the release tags to sync. It tags the commit that started the run if a beta still needs those changes. Knotless mirrors the new tag, which starts the existing Xcode Cloud workflow. Run a workflow manually

Make sure that the build reaches TestFlight with the expected notes. Run the workflow again on the same commit and make sure that it skips tagging. Then set the Actions variable TESTFLIGHT_NIGHTLY_ENABLED to true. GitHub schedules the job daily at 18:17 in Europe/Rome. GitHub Actions schedules

Prepare an App Store build

When you are ready to prepare an App Store build, create a separate App Store workflow that starts on tags beginning with v. Enable Restrict Editing in General and select Clean in Environment. Add an iOS Archive action with Deployment Preparation set to TestFlight and App Store. Apple’s distribution workflow guide

From the Knotless checkout, run just release to push a tag such as v0.1.0. Xcode Cloud prepares the build for submission. Submit the build for review in App Store Connect when you are ready. Apple’s submission guide

Version tags and retries

Before the first App Store release, both commands use the version from the latest beta tag. If there are no beta tags, they use MARKETING_VERSION from Configuration/Version.xcconfig. After the first App Store tag, AutoTag reads Conventional Commits since the last App Store tag. TestFlight tags add a beta number. Both commands reuse an existing tag for the same commit and workflow.

If the mirror push fails, open the Knotless check log. After you fix the cause, rerun the workflow for the tag.

knotless run rerun knotless://geesawra.industries/old-fella \
  --ref refs/tags/testflight/v0.1.0-beta.1 --workflow xcode-cloud

If GitHub already holds the tag, find its existing build under Xcode Cloud → Builds.