-
Notifications
You must be signed in to change notification settings - Fork 465
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
noninteractive mode broken? #75
Comments
I can confirm that --noninteractive doesn't appear to do anything in 1.2.0. |
Fixed in v1.3.0 in senthilmanick/ios-deploy |
Fixed the hang when the device is locked. When the device is locked, we get empty packets in the server. Now fixed by closing both the lldb and server sockets. Also after safequit, we need to detach to make the "justlaunch" option to be less error prone. Multiple bug fixes: 1. When multiple devices are connected, the detect was not listing all the devices ios-deploy -c -t 1 2. Fixes for issue #75 - non-interactive mode broken lldb and ios-deploy may still be running ios-deploy -b ... -d -I -L 3. Fixes for issue #60 - -L option not working properly ios-deploy will not quit or sometimes hang 4. When multiple devices are connected, cannot use -i option to specify the device ios-deploy -b ... -i -d -I -L 5. Allow timeout when downloading
@senthilmanick I can't verify that this is fixed even after the merge. How are your command line args for this test? |
Ok confirmed it works in 1.3.0 |
Fixed in 1.3.0, release pending |
Hi,
My environment:
I'm using ios-deploy to perform automated smoke-testing of our application on device. I have found the --noninteractive mode unreliable or just plain broken as ios-deploy doesn't seem to detect crashes or application exit even when this option is enabled. I've tried to investigate a bit and it doesn't seem to be receiving any process event when the application crashes (in the autoexit lldb custom command). It also doesn't seem to detect when my application has quit or been shutdown on device, so ios-deploy just hangs in there and I need to manually kill it.
Are there any known issues with --noninteractive mode at the moment?
The text was updated successfully, but these errors were encountered: