[CP-beta][native assets] Bump minimum iOS version from 13 to 15 - #192507
Merged
Conversation
Updates `targetIOSVersion` constant to 15 in native_assets. Fixes [https://github.com/dart-lang/native/issues/3594](https://github.com/dart-lang/native/issues/3594). Co-authored-by: Elijah Okoroh <okorohelijah@google.com>
Contributor
Author
|
@okorohelijah please fill out the PR description above, afterwards the release team will review this request. |
|
This pull request was opened from and to a release candidate branch. This should only be done as part of the official Flutter release process. If you are attempting to make a regular contribution to the Flutter project, please close this PR and follow the instructions at Tree Hygiene for detailed instructions on contributing to Flutter. Reviewers: Use caution before merging pull requests to release branches. Ensure the proper procedure has been followed. |
jmagman
approved these changes
Sep 9, 2026
walley892
approved these changes
Sep 9, 2026
auto-submit
Bot
merged commit Sep 9, 2026
c9306d5
into
flutter:flutter-3.48-candidate.0
12 checks passed
flutteractionsbot
deleted the
cp-beta-9983248b6be0d3d2afeab396837fc3790ed3c610
branch
September 9, 2026 21:02
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
4 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.
This pull request is created by automatic cherry pick workflow
Please fill in the form below, and a flutter domain expert will evaluate this cherry pick request.
Issue Link:
What is the link to the issue this cherry-pick is addressing?
dart-lang/native#3594
Impact Description:
What is the impact (ex. visual jank on Samsung phones, app crash, cannot ship an iOS app)?
Does it impact development (ex. flutter doctor crashes when Android Studio is installed),
or the shipping of production apps (the app crashes on launch).
This information is for domain experts and release engineers to understand the consequences of saying yes or no to the cherry pick.
Developers cannot submit iOS apps to App Store Connect / TestFlight when using native assets compiled with -mios-version-min >= 14 (such as libraries using C++20).
This impacts shipping production apps. Apple rejects the uploaded IPA with error ITMS-90208: Invalid Bundle because flutter_tools generates a framework Info.plist with MinimumOSVersion = 13.0, conflicting with the binary's higher OS requirement.
Changelog Description:
Explain this cherry pick:
See best practices for examples.
flutter/191964: On iOS, apps bundling native assets fail App Store submission when native libraries are compiled with deployment targets above iOS 13.
Workaround:
Is there a workaround for this issue?
Manually edit Info.plist inside Runner.app/Frameworks/.framework/Info.plist in the built archive to set MinimumOSVersion to 15.0, and re-sign the framework and app before uploading to App Store Connect
Risk:
What is the risk level of this cherry-pick?
Test Coverage:
Are you confident that your fix is well-tested by automated tests?
Validation Steps:
What are the steps to validate that this fix works?
3)Confirm it reads "15.0" instead of "13.0"