Skip to content
C.W.K.
Stream
Lesson 03 of 04 · published

A Cable Is a Build Check

~12 min · testflight, delivery, signing, ios

Level 0Spark
0 XP0/36 lessons0/12 achievements
0/100 XP to next level100 XP to go0% complete

The Instinct Is Real and Cross-Brain

A cable install — Apple Development signing, a wire, an unlocked phone in hand — feels like shipping. It is a build check. It expires in seven days. It reaches one device. It cannot launch if the phone is locked, which is how a session can "install" an app Dad never opened. TestFlight signs for a year against the team, lands over the air on every enrolled device, and gives an install he can accept on his own schedule. That is delivery. The family already has the pipeline. Firebrand is the declared canonical iOS reference. Smolder vendors the same script from Sibling Kit, with this app's facts in a local config. Change the pipeline in the kit. Change the facts here.

The recorded failure this rule exists for is not theoretical. A session finished the first usable mobile version, signed it Apple Development, installed it over a cable, and logged TestFlight as a remaining gate. The knowledge existed, in writing, in the family, twelve days earlier. It did not fire. Name the instinct before the work starts, not after Dad points at TestFlight.

First Build Is Not a Special Case

"The first build of a new app can be a cable, TestFlight later" is how later never arrives. The pipeline is already built. One paid Apple Developer team carries the family. The Macs' self-signed identity has no iOS equivalent, which is why the cable feels like the only door. It is the wrong door.

A cable is a build check. TestFlight is delivery. First builds are not exempt. The family's script is the family's, not this repo's to rewrite.

Code

Two signatures, two audiences, one of them is not delivery·text
APPLE DEVELOPMENT + CABLE
  expiry:    7 days
  audience:  one unlocked device, wire in hand
  launches:  only if the phone is unlocked at install-time
  verdict:   build check

TESTFLIGHT (internal group)
  expiry:    90 days per build (upload again)
  audience:  every enrolled device, over the air
  accept:    on Dad's schedule, not yours
  verdict:   delivery, once the build is INSTALLED on the device

# The pipeline lives in Sibling Kit.
# This app's facts (bundle, scheme, team) live beside the app.
# --plan checks every fact without building.

External links

Exercise

A session says "iOS is on the phone" after a cable install, and lists TestFlight under remaining. Rewrite the report as four short lines using only the words build-check, uploaded, processed, assigned, installed. Circle which line is actually true. If installed is not circled, the app is not delivered.
Hint
Cable install can make "installed" true on one device and still be the wrong channel. Delivery for this family is TestFlight-installed, on the enrolled devices, in the internal group.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.