[various] Scrub pre-iOS-13 code (#9849)
For all packages that had conditionals to support iOS <13:
- Update the min Flutter version to 3.35, which requires iOS 13
- Remove the conditional logic
- Update all the project metadata to require iOS 13+ (and macOS 10.15+ where applicable)
There is also some minor cleanup in in_app_purchase_storekit; just removing conditionals would have left cases where we were unnecessarily constructing dictionaries dynamically, so I folded them into the initial dictionary construction, and while doing that I noticed some cases where we were doing other unnecessary dynamic construction (maybe due to previous OS conditionals?) so I updated those as well. And then I noticed some inconsistency in use of WithCapacity: and updated those cases to be consistent. Lastly, I fixed a few stale comments that didn't reflect the current state of the code.
Includes autoformat changes, since updating the min Dart SDK opts into some formatter changes.
Fixes https://github.com/flutter/flutter/issues/167735
## Pre-Review Checklist
**Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.
[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.
[various] Scrub pre-iOS-13 code (#9849)
For all packages that had conditionals to support iOS <13:
- Update the min Flutter version to 3.35, which requires iOS 13
- Remove the conditional logic
- Update all the project metadata to require iOS 13+ (and macOS 10.15+ where applicable)
There is also some minor cleanup in in_app_purchase_storekit; just removing conditionals would have left cases where we were unnecessarily constructing dictionaries dynamically, so I folded them into the initial dictionary construction, and while doing that I noticed some cases where we were doing other unnecessary dynamic construction (maybe due to previous OS conditionals?) so I updated those as well. And then I noticed some inconsistency in use of WithCapacity: and updated those cases to be consistent. Lastly, I fixed a few stale comments that didn't reflect the current state of the code.
Includes autoformat changes, since updating the min Dart SDK opts into some formatter changes.
Fixes https://github.com/flutter/flutter/issues/167735
## Pre-Review Checklist
**Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.
[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.
Remove "All right reserved" from all files (#10066)
Per guidance from legal on current preferred practice, remove "All rights reserved" from all LICENSE files and header blocks, and update the repo tool check accordingly.
[camera_avfoundation] Wrappers swift migration - part 4 (#10440)
Migrates camera wrappers as part of https://github.com/flutter/flutter/issues/119109
This PR migrates wrappers to Swift:
* FLTCaptureConnection
* FLTCaptureDeviceFormat
* FLTAssetWriter
In line with Swift conventions, the FLT prefixes are removed. The Default class implementations are replaced with protocol conformance on base AV classes.
## Pre-Review Checklist
**Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.
[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.
[various] Scrub pre-iOS-13 code (#9849)
For all packages that had conditionals to support iOS <13:
- Update the min Flutter version to 3.35, which requires iOS 13
- Remove the conditional logic
- Update all the project metadata to require iOS 13+ (and macOS 10.15+ where applicable)
There is also some minor cleanup in in_app_purchase_storekit; just removing conditionals would have left cases where we were unnecessarily constructing dictionaries dynamically, so I folded them into the initial dictionary construction, and while doing that I noticed some cases where we were doing other unnecessary dynamic construction (maybe due to previous OS conditionals?) so I updated those as well. And then I noticed some inconsistency in use of WithCapacity: and updated those cases to be consistent. Lastly, I fixed a few stale comments that didn't reflect the current state of the code.
Includes autoformat changes, since updating the min Dart SDK opts into some formatter changes.
Fixes https://github.com/flutter/flutter/issues/167735
## Pre-Review Checklist
**Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.
[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.