apple signing ensure with automatic signing only adds capabilities (no profiles or certificates; the dry run says so) and lists unused storebound profiles with the exact delete command, never run; every capability write is read back (lag retries, timeout) and fails with the API answers when one did not stick; apple status, signing status and validate compare the App ID, apple.signing.capabilities and the iOS project's entitlements (CODE_SIGN_ENTITLEMENTS too) and name what is missing where; api writes outside a terminal say TTY by design and name the dedicated command; pitfalls 64-66; tests
This commit is contained in:
parent
357319a775
commit
daae3715bf
12 changed files with 463 additions and 23 deletions
12
CHANGELOG.md
12
CHANGELOG.md
|
|
@ -2,6 +2,18 @@
|
|||
|
||||
## Unreleased
|
||||
|
||||
- **`apple signing ensure` with automatic signing creates no profiles or certificates.** With `signing.style:
|
||||
automatic` (the default) it only adds missing capabilities to the App ID; Xcode owns certificates and profiles, and
|
||||
the dry run says so. Provisioning profiles storebound made that nothing uses are listed by name with the exact
|
||||
delete command (never run by storebound).
|
||||
- **Capability writes are read back.** After adding a capability, `ensure` reads the App ID again (a few tries,
|
||||
about 45 s at most) and fails with the API's answers when one is missing, instead of reporting success.
|
||||
- **Capabilities compared in three places.** `apple status`, `apple signing status` / `ensure --dry` and `validate`
|
||||
compare the App ID, `apple.signing.capabilities` and the iOS project's `.entitlements` (push, Game Center,
|
||||
associated domains, Sign in with Apple, iCloud, app groups, ...; also an entitlements file not set in
|
||||
CODE_SIGN_ENTITLEMENTS) and name what is missing where.
|
||||
- **`storebound api` writes outside a terminal** say that they need an interactive terminal by design and name the
|
||||
dedicated command for common operations (bundle id capabilities: `apple signing ensure`, IAPs, listing, ...).
|
||||
- **`--json` prints only JSON on stdout.** Every command run with `--json` sends its log, step and table lines to
|
||||
stderr (one place: `withJsonOutput` in cli/lib/log.ts, wrapped around every command); the last commands that printed
|
||||
JSON with console.log use `printJson`. A test runs every command that reads `--json` against the fake stores and
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue