v1.2.1
Headroom 1.2.1 (build 176).
What changed
Fixed
- Multi-Mac over iCloud now works in released builds. Every release up to 1.2.0
was notarized without the iCloud provisioning profile, so the published app
carried no CloudKit entitlement and Settings reported iCloud as unavailable
on every Mac that downloaded one. Nothing was red: the release was properly
signed and notarized, and only a note in the build log said the feature was
off. The workflow now embeds the profile, and refuses one whose team does not
match the signing certificate. An app downloaded before this release does not
gain iCloud, because entitlements are sealed into a signature. - Settings no longer claims that signed releases can use iCloud. That was false
for exactly the people reading it on a notarized release, and sent them to
download another copy of what they already had. A local build and a release
built without the profile now say different things. - The iOS archive stopped minting a
Created via APIdevelopment certificate
on every run, which walked the team toward its certificate cap and then
failed the archive itself withChoose a certificate to revoke. - iOS release builds no longer break on SDK-specific
CODE_SIGN_IDENTITYkeys
written into the pbxproj unquoted.
macOS
Download Headroom-macOS.zip, unzip, open Headroom.app.
Notarized — Gatekeeper should accept it on first open.
On first launch the Welcome sheet starts the bundled host automatically. Confirm Claude / Codex / Cursor, then Continue.
iPhone
Install via TestFlight.
Pairing uses the mobile token (Mac Settings → Copy mobile token), not the host token used by the ESP32.
What's Changed
- fix(ci): iOS archive manual signing (TestFlight) by @michellzappa in #4
- fix(ci): quote pbxproj CODE_SIGN_IDENTITY sdk keys by @michellzappa in #5
- fix(test): expect claude-status in AI sources section by @michellzappa in #6
- fix(ci): embed the iCloud profile in released macOS builds by @michellzappa in #7
Full Changelog: v1.2.0...v1.2.1