Repository navigation
fix(release): retry transient Apple ticket connection failures - #3409
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
macOS ARM64 packaging completed compilation, Developer ID signing and Apple notarization, then failed because CloudKit dropped the ticket-validation connection (
NSURLErrorDomain Code=-1005, stapler exit 68). A single transport error discarded a fully built release package.Retry stapler validation/stapling at most three times, with 10/20-second delays, only when both that exit code and the observed connection-loss diagnostic match. Invalid tickets, other exit codes, signing failures, Gatekeeper rejection and notarization submission failures still fail normally. Retry the individual stapler command so DMG notarization is submitted only once.
For immutable-tag rebuilds, load the two verification scripts from the pinned workflow revision into a temporary directory. The product checkout stays on its original tag. This ensures the 1.0.6 rebuild actually uses the corrected verification policy without moving its tag or replacing signed artifacts. GitHub documents
github.workflow_shaas the workflow file commit SHA.Validation:
pnpm run check:github-config— 40 passed, 1 unrelated environment-dependent skip. Includes transient/exhausted app and DMG ticket checks, invalid tickets, other exit codes, signature/Gatekeeper/submission rejection, and a real shallow Git checkout test proving pinned verification, unchanged product HEAD and unchanged artifact bytes.node --test scripts/ci/verify-macos-microphone.test.mjs— 4 passed with disposable locally signed bundles.bash -n scripts/ci/verify-macos-signing.sh,pnpm run check:repo-hygiene, andgit diff --checkpassed.Observed failure: https://github.com/GCWing/OpenBitFun/actions/runs/38704563620/job/116320759304
AI-assisted; lightly tested with focused verification fixtures. Fixtures do not prove live Apple service availability. Full signed packaging remains the release verification step. Remote workspace, remote control, Peer Device Mode and Detached Dispatch were not exercised; runtime code, native mobile releases and persisted shapes are unchanged.