Repository navigation
Conversation
Member
Author
|
Hitting flutter/flutter#170438 |
jmagman
force-pushed
the
ios-deprecation-check
branch
from
June 26, 2025 17:21
32b65d5 to
79b5b4f
Compare
11 tasks done
Member
Author
|
Hitting flutter/flutter#105490 |
jmagman
force-pushed
the
ios-deprecation-check
branch
from
June 26, 2025 18:12
b07c22f to
b9da864
Compare
11 tasks done
jmagman
force-pushed
the
ios-deprecation-check
branch
from
August 4, 2025 23:04
d03b600 to
66316d5
Compare
This was referenced Aug 4, 2025
Closed
jmagman
force-pushed
the
ios-deprecation-check
branch
from
September 16, 2025 05:40
861ad54 to
d8514ae
Compare
|
clang: error: conflicting deployment targets, both '26.0' and '25.0' are present in environment |
Contributor
|
Greetings from stale PR triage! 👋 |
Member
Author
|
Closing until we get the blockers fixed. |
Member
Author
|
Hitting flutter/flutter#181291 |
11 tasks done
auto-submit Bot
pushed a commit
that referenced
this pull request
Oct 14, 2026
…'videoRotationAngle' on iOS 17+ (#13247) Remove deprecated AVFoundation camera APIs, replace with iOS 17+ API `videoRotationAngle`. This will allow us to check for deprecations higher than iOS 17 in CI, like #9431. Migrate CameraSetDeviceOrientationTests to Swift Testing while we're at it to take advantage of parameterization. I tested this manually and orientation worked as expected. I would upload a video but it seems camera capture doesn't work when connected through a DeviceHub session (presumably a privacy protection) and QuickTime stopped the recording whenever there was an orientation change, so you'll have to trust me it worked manually. Fixes flutter/flutter#170438 ## 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.
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
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.
I tried this in #7542 and abandoned it because of the integration_test deprecation. That should no longer occur after flutter/flutter#173251.
Exclude camera until flutter/flutter#170438 is completed.
Exclude in_app_purchase_storekit until flutter/flutter#105490 is completed.
There are more iOS 18 deprecation warnings to dig through, so let's get up to 17 and go from there.
Last bump at #7431
Pre-Review Checklist
[shared_preferences]pubspec.yamlwith an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under1.CHANGELOG.mdto add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under1.///).If you need help, consider asking for advice on the #hackers-new channel on Discord.
Footnotes
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩2 ↩3