Separate attached and wireless devices#122615
Separate attached and wireless devices#122615auto-submit[bot] merged 2 commits intoflutter:masterfrom
Conversation
| final IOSDeviceConnectionInterface interfaceType; | ||
|
|
||
| @override | ||
| DeviceConnectionInterface get connectionInterface { |
There was a problem hiding this comment.
I know you added this enum in a previous refactor PR #121359, but is there any reason to maintain both DeviceConnectionInterface and IOSDeviceConnectionInterface? Can we swap the iOS device to use DeviceConnectionInterface instead, with the none either removed, or added to DeviceConnectionInterface?
There was a problem hiding this comment.
Good point, on further inspection, I think we can safely get rid of IOSDeviceConnectionInterface. The none case is for simulators, which we consider attached and aren't even included in IOSDevice. The "unknown future interfaces" gets categorized as usb currently, which will get changed to attached.
flutter/packages/flutter_tools/lib/src/macos/xcdevice.dart
Lines 360 to 371 in fcf1134
This PR includes 4 changes:
flutter run.flutter devicescommand.IOSDeviceConnectionInterfacewithDeviceConnectionInterfacesince it's no longer needed.IOSDeviceConnectionInterface.network->DeviceConnectionInterface.wirelessIOSDeviceConnectionInterface.usb->DeviceConnectionInterface.attachedIOSDeviceConnectionInterface.none->DeviceConnectionInterface.attachedNote: This PR does not include updates for extended search for wireless iOS devices.
Part 3 in breakdown of #121262.
Fixes #119271.
Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.