Skip to content

Fix TestFlight signing so a post-July build can upload - #150

Merged
sanylax2 merged 1 commit into
mainfrom
cursor/testflight-newer-build-f202
Sep 14, 2026
Merged

sanylax2 merged 1 commit into
mainfrom
cursor/testflight-newer-build-f202

Conversation

@sanylax0

Copy link
Copy Markdown
Collaborator

TestFlight on your phone is still 0.1.0 build 130 (Jul 18) because every GitHub Actions archive since late July has died at signing: ephemeral runners minted a new Apple Development cert each run until the account hit Apple’s cap (Choose a certificate to revoke + missing development profiles).

This PR:

  • Archives as Release with Apple Distribution so CI stops asking for development certs
  • Sets CFBundleVersion to 1000 + github.run_number so the upload is newer than TestFlight build 130 (raw run_number is still in the 30s)

After merge, the TestFlight workflow on main should upload a build like 0.1.0 (103x). Pull to refresh in TestFlight once processing finishes (~10–20 min). If archive still fails with the cert-cap error, revoke unused Apple Development certificates at developer.apple.com/account/resources/certificates and re-run the TestFlight workflow.

Slack Thread

Open in Web Open in Cursor 

Ephemeral runners were minting Apple Development certs until the account hit the cap, so every archive since late July failed. Force Apple Distribution, and set CFBundleVersion to 1000+run_number so uploads beat TestFlight build 130.

Co-authored-by: sanylax0 <sanylax0@users.noreply.github.com>
@sanylax2
sanylax2 merged commit a8fc915 into main Sep 14, 2026
4 checks passed
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.

3 participants