Uh oh!
There was an error while loading. Please reload this page.
[camera_avfoundation] Implementation swift migration - part 2 - #9007
Conversation
aa4269d to
8be6136CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
8be6136 to
859ad13Compare
hellohuanlin
left a comment
There was a problem hiding this comment.
not a complete review, left a few questions
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
859ad13 to
63292b4CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
63292b4 to
2898d01CompareUh oh!
There was an error while loading. Please reload this page.
flutter/packages@8d01cd9...250ee0d 2025-05-01 robert.odrowaz@leancode.pl [camera_avfoundation] Implementation swift migration - part 2 (flutter/packages#9007) 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 flutter-ecosystem@google.com 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
…r#9007) Migrates camera implementation as part of flutter/flutter#119109 This PR migrates `CameraPlugin` class. While it wasn't the goal of this PR it partially resolves the [issue](flutter/flutter#162376) regarding switching the camera during recording. The main problem there was that the capture device wasn't actually changed because the camera name passed to the `FLTCam.setDescriptionWhileRecording` wasn't used and instead a `captureDeviceFactory` was called which returned a capture device with the same name as during the initial set up. In this pr "named" capture device factory is propagated to `FLTCam` allowing passing the new capture device name during in `setDescriptionWhileRecording`. ## Pre-Review Checklist [^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.
…r#9007) Migrates camera implementation as part of flutter/flutter#119109 This PR migrates `CameraPlugin` class. While it wasn't the goal of this PR it partially resolves the [issue](flutter/flutter#162376) regarding switching the camera during recording. The main problem there was that the capture device wasn't actually changed because the camera name passed to the `FLTCam.setDescriptionWhileRecording` wasn't used and instead a `captureDeviceFactory` was called which returned a capture device with the same name as during the initial set up. In this pr "named" capture device factory is propagated to `FLTCam` allowing passing the new capture device name during in `setDescriptionWhileRecording`. ## Pre-Review Checklist [^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.
…r#9007) Migrates camera implementation as part of flutter/flutter#119109 This PR migrates `CameraPlugin` class. While it wasn't the goal of this PR it partially resolves the [issue](flutter/flutter#162376) regarding switching the camera during recording. The main problem there was that the capture device wasn't actually changed because the camera name passed to the `FLTCam.setDescriptionWhileRecording` wasn't used and instead a `captureDeviceFactory` was called which returned a capture device with the same name as during the initial set up. In this pr "named" capture device factory is propagated to `FLTCam` allowing passing the new capture device name during in `setDescriptionWhileRecording`. ## Pre-Review Checklist [^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.
…r#9007) Migrates camera implementation as part of flutter/flutter#119109 This PR migrates `CameraPlugin` class. While it wasn't the goal of this PR it partially resolves the [issue](flutter/flutter#162376) regarding switching the camera during recording. The main problem there was that the capture device wasn't actually changed because the camera name passed to the `FLTCam.setDescriptionWhileRecording` wasn't used and instead a `captureDeviceFactory` was called which returned a capture device with the same name as during the initial set up. In this pr "named" capture device factory is propagated to `FLTCam` allowing passing the new capture device name during in `setDescriptionWhileRecording`. ## Pre-Review Checklist [^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.
…r#9007) Migrates camera implementation as part of flutter/flutter#119109 This PR migrates `CameraPlugin` class. While it wasn't the goal of this PR it partially resolves the [issue](flutter/flutter#162376) regarding switching the camera during recording. The main problem there was that the capture device wasn't actually changed because the camera name passed to the `FLTCam.setDescriptionWhileRecording` wasn't used and instead a `captureDeviceFactory` was called which returned a capture device with the same name as during the initial set up. In this pr "named" capture device factory is propagated to `FLTCam` allowing passing the new capture device name during in `setDescriptionWhileRecording`. ## Pre-Review Checklist [^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.
Migrates camera implementation as part of flutter/flutter#119109
This PR migrates
CameraPluginclass.While it wasn't the goal of this PR it partially resolves the issue regarding switching the camera during recording. The main problem there was that the capture device wasn't actually changed because the camera name passed to the
FLTCam.setDescriptionWhileRecordingwasn't used and instead acaptureDeviceFactorywas called which returned a capture device with the same name as during the initial set up. In this pr "named" capture device factory is propagated toFLTCamallowing passing the new capture device name during insetDescriptionWhileRecording.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