fix: Use devicectl while listing available device udids #2648
Conversation
| * @returns {Promise<string[]>} | ||
| */ | ||
| export async function getConnectedDevices() { | ||
| return await utilities.getConnectedDevices(); |
There was a problem hiding this comment.
The devicectl command could have a situation that doesn't work or conflict if the same env has core device service injected (e.g. 3rd party tools) So, this could be a breaking change for such a condition.
Currently, this may help only for tvOS (and env which doesn't expose usbmuxd for wifi-connected devices), thus maybe it makes sense to add a new capability to use devicectl prior to appium-ios-device
There was a problem hiding this comment.
I've updated the logic to use an env flag instead. I do't want to introduce a new capability as I expect this solution to be temporary until we fully ditch appium-ios-device and switch to appium-ios-remotexpc usage
## [10.4.2](v10.4.1...v10.4.2) (2025-11-03) ### Bug Fixes * Use devicectl while listing available device udids ([#2648](#2648)) ([5953a97](5953a97))
|
🎉 This PR is included in version 10.4.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
2 participants
This should make the workaround #2194 obsolete