You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been unable to run iOS tests on AWS when using Sylph. When running, the app builds and is uploaded, Flutter is installed on AWS, but when Sylph runs flutter drive, it returns with the error message No devices found.. I forked the repo and added a flutter devices command, and am seeing the same message.
Anyone have any idea what to do to encourage Flutter to see the device that's connected?
The text was updated successfully, but these errors were encountered:
I have the same issue. I am using Flutter 1.22.4 and flutter doctor returns No devices available when running iOS tests. @kalebhermes Have you found any solution?
After some more investigation, I found out the devices are visible on Flutter version v1.12.13+hotfix.9.
But when I switched to the 1.17 or later it will no longer detect any device.
The only way I was able to detect the device on new Flutter versions is by adding --device-timeout argument: flutter devices --device-timeout 60
It returns:
1 connected device:
9905949316 (mobile) • 00008030000C50A13EF2802E • ios • iOS 13.3.1
• Error: 9905949316 is busy: Preparing debugger support for 9905949316. Xcode will continue when 9905949316 is finished. (code -10)
But it doesn't detect the device when running flutter driver, even if I also add the --device-timeout.
Has anyone managed to make AWS device farm work with the new Flutter versions?
I've been unable to run iOS tests on AWS when using Sylph. When running, the app builds and is uploaded, Flutter is installed on AWS, but when Sylph runs
flutter drive
, it returns with the error messageNo devices found.
. I forked the repo and added aflutter devices
command, and am seeing the same message.Anyone have any idea what to do to encourage Flutter to see the device that's connected?
The text was updated successfully, but these errors were encountered: