← ClaudeAtlas

macos-direct-distributionlisted

Set up direct (outside the Mac App Store) distribution for a macOS Xcode app: a dedicated "Direct" target — sandbox off, hardened runtime on, a DIRECT flag, direct-only frameworks linked to it alone — wired to Sparkle auto-updates with EdDSA signing keys, a SUFeedURL, a "Check for Updates" menu item and an appcast signing script — and, for selling that build, a licence key from a hosted checkout, kept out of the App Store build. Use whenever the user wants automatic updates for a Mac app sold outside the App Store ("הפצה ישירה", "עדכונים אוטומטיים"), add Sparkle, create a second non-MAS target alongside an App Store build, set up an appcast, sell the direct build with a licence key ("מפתח רישיון", Lemon Squeezy), or ask how to keep Sparkle or licensing out of the App Store build. Pairs with `notarize-and-distribute`, which builds the signed DMG this skill's appcast points at.
yybd/app-factory · ★ 5 · AI & Automation · score 77
Install: claude install-skill yybd/app-factory
# Direct distribution + auto-updates for a macOS app Give a macOS app a second distribution channel — a notarized DMG downloaded from your own site — that lives **alongside** the App Store build from one codebase, and updates itself via Sparkle. This skill creates the build target and the update mechanism; the **notarize-and-distribute** skill builds the signed DMG. The hard part is keeping the two channels cleanly separated. The key constraint: **a linked framework is embedded per-target, not per-configuration**, so keeping Sparkle out of the App Store build (required by Guideline 2.4.5) means the direct build needs its own *target*, not just a build config. See [references/xcode-target.md](references/xcode-target.md) for the full rationale. ## Prerequisites - **Tools:** Xcode 16, and the `xcodeproj` Ruby gem (`gem install xcodeproj`, or via the project's `bundle`) — the scripts use it to edit the project safely. Sparkle itself is added as a package dependency, not installed. - **Credentials:** a Developer ID Application certificate, plus the Sparkle EdDSA key pair this skill generates and stores in the keychain. Notarization credentials belong to `notarize-and-distribute`. - **Which key or certificate:** if `$KEYS_ROOT/APPLE.md` exists, look there first — the owner's map of the team, each certificate and its expiry, and which App Store Connect key under `$KEYS_ROOT/store-api/appstoreconnect/<name>/` serves what (no secrets). `apple-credentials` reads it, r