-
Notifications
You must be signed in to change notification settings - Fork 3.6k
[various] Update minimum iOS versions to 12.0 #5902
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Changelog override: the packages missing changelog changes just have uninteresting example project changes. |
jmagman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change LGTM, thanks for doing it.
| inputPaths = ( | ||
| "${PODS_ROOT}/Target Support Files/Pods-Runner/Pods-Runner-resources.sh", | ||
| "${PODS_ROOT}/GoogleMaps/Maps/Frameworks/GoogleMaps.framework/Resources/GoogleMaps.bundle", | ||
| "${PODS_CONFIGURATION_BUILD_DIR}/google_maps_flutter_ios/google_maps_flutter_ios_privacy.bundle", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't realize adding the privacy bundle would update the host Xcode project, not just the generated Pod project.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this is the non-use_frameworks version.
It's not really clear what the "right" behavior for privacy manifests with non-framework pods even is (not just in Flutter, but in general). Are app developers supposed to be responsible for copying any privacy details into their own manifest manually? Should Cocoapods in theory have magic tooling to merge them in the app's manifest automatically?
I'm assuming in the long term the answer is to use SPM, and the new static frameworks system, at which point presumably Xcode magic will handle it. But for now, having them end up in a weird bundle is kind of the only option that people have found for shimming this into Cocoapods (if you don't use a bundle, it instead stomps the main privacy manifest, which is obviously worse). We'll see what happens with this when the validation tooling goes live 🤷🏻
Piinks
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
flutter/packages@7dd0fcb...1a2b780 2024-01-17 98614782+auto-submit[bot]@users.noreply.github.com Reverts "[ci] Run check_podspecs on arm Mac bots" (flutter/packages#5909) 2024-01-17 [email protected] [various] Update minimum iOS versions to 12.0 (flutter/packages#5902) 2024-01-16 [email protected] [ci] Run check_podspecs on arm Mac bots (flutter/packages#5885) 2024-01-16 [email protected] [pigeon] Fix pigeon test generation missing wrapResponse method. (flutter/packages#5903) 2024-01-16 [email protected] Roll Flutter from 1a2c315 to 8e94423 (2 revisions) (flutter/packages#5897) 2024-01-16 49699333+dependabot[bot]@users.noreply.github.com Bump actions/upload-artifact from 3.1.3 to 4.1.0 (flutter/packages#5896) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages-flutter-autoroll Please CC [email protected],[email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
This makes the following mass changes:
The only code changes are:
@availablechecks inin_app_purchase_storekitthat had become no-ops with the support change!incamera_avfoundationDart code, which is no longer necessary due to changes in nullable field promotion in newer versions of Dart.These changes are version-exempt per repo policy, so the changelog changes all use NEXT.
Pre-launch Checklist
dart format.)[shared_preferences]pubspec.yamlwith an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.CHANGELOG.mdto add a description of the change, following repository CHANGELOG style.///).