https://hobbyworker.me/en/series/shipping-a-macos-app-to-the-mac-app-store/ Recent content in Shipping a MacOS App to the Mac App Store on hobbyworker취미생활자 Hugo en 2026 hobbyworker Tue, 19 May 2026 00:00:00 +0000 https://hobbyworker.me/en/dev/2026-05-19-distribute-macos-app-mas-3-export-and-app-store-connect/ Tue, 19 May 2026 00:00:00 +0000 https://hobbyworker.me/en/dev/2026-05-19-distribute-macos-app-mas-3-export-and-app-store-connect/ Once you've finished the MAS build target and the configuration and code branching, it's time to set up the path for getting that build onto the App Store. Using the example app FocusTimer, this post wraps up the series by covering how to write an ExportOptions-MAS.plist for upload, register an app record in App Store Connect, and verify the build so the two channels stay unbroken. https://hobbyworker.me/en/dev/2026-05-18-distribute-macos-app-mas-2-build-config-and-code/ Mon, 18 May 2026 00:00:00 +0000 https://hobbyworker.me/en/dev/2026-05-18-distribute-macos-app-mas-2-build-config-and-code/ Once you've created a build target for MAS, you need to split the configuration files and code so that target actually follows the App Store rules. Using the example app FocusTimer, this post walks through creating MAS-only entitlements and Info.plist files, aligning the build settings, and branching the automatic update code with #if canImport(Sparkle). https://hobbyworker.me/en/dev/2026-05-17-distribute-macos-app-mas-1-target-setup/ Sun, 17 May 2026 00:00:00 +0000 https://hobbyworker.me/en/dev/2026-05-17-distribute-macos-app-mas-1-target-setup/ Shipping a macOS app to the Mac App Store requires a build target separate from the one used for direct distribution, because App Store review forbids self-contained automatic updaters like Sparkle. Using the example app FocusTimer, this post walks through registering a MAS-only Bundle ID, duplicating the build target in Xcode, and handling the cleanup burden that duplication leaves behind.