-
Notifications
You must be signed in to change notification settings - Fork 467
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
Bug or intended change of exit code for ios-deploy -c #80
Comments
Seems to me a regression - I'll test and put out a patch release soon. Only a successful connection should be zero |
1.3.1 published. |
Curly brackets are programmer's best friend ;) |
See #11 latest comments. Flaw in the patch. |
Also --debug needs to be turned on, if not you'll get a seg fault. iso-deploy will add it implicitly. |
1.3.2 published to fix 1.3.1 :) |
Shazron, |
No this is the true fix. Tested |
I can confirm, 1.3.2 resolved the issue in question. |
Scenario: iPhone is not connected via USB to Mac. No other devices or simulators are connected / running.
With 1.2.0:
$ ios-deploy -c --timeout 2
[....] Waiting up to 2 seconds for iOS device to be connected
[....] Timed out waiting for device.
$ echo $?
253
With latest (1.3.0):
$ ios-deploy -c --timeout 2
[....] Waiting up to 2 seconds for iOS device to be connected
[....] No more devices found.
$ echo $?
0
This change breaks a script that depends on checking the exit code.
How would one proceed to resolve this ( and not resort to manual parsing of the output )?
The text was updated successfully, but these errors were encountered: