Repository navigation
fix: raise macOS deployment target to 12.0 - #576
Merged
m1sterc001guy merged 1 commit intoSep 22, 2026
Merged
Conversation
Xcode 27 rejects deployment targets below 12.0 as a hard error, so the 10.15 template default fails every target in Runner and Pods. Plugin resource bundles keep their podspec minimums (10.11-10.14), so the Podfile forces them up as well. The Rust build now pins MACOSX_DEPLOYMENT_TARGET too: `nix develop` exports 14.0, which silently made the dylib require macOS 14 whatever the Xcode project declared.
m1sterc001guy
approved these changes
Sep 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
just run-macosfails on Xcode 27 with:Xcode 27's SDK sets the minimum to 12.0 and treats anything lower as a hard error, where older Xcodes only warned. The project was still on Flutter's 10.15 template default, and the plugin
*_privacyresource bundles carry their podspec minimums (10.11–10.14), which Flutter's podhelper doesn't touch.Changes:
project.pbxprojandPodfileplatform → 12.0;post_installforces every pod target to 12.0 so the resource bundles pass toobuild-macos.sh/package-macos.shexportMACOSX_DEPLOYMENT_TARGET=12.0beforecargo build.nix developexports 14.0, which silently madelibecashapp.dylibrequire macOS 14 regardless of what the app declared — same approach asIPHONEOS_DEPLOYMENT_TARGETinbuild-rust-ios.shVerified:
just build-macosinnix developproduces aminos 12.0dylib with no linker warnings;flutter build macos --debugsucceeds with no deployment-target diagnostics; app binary, embedded framework and all 48 Pods configurations report 12.0.