Releases: ios-control/ios-deploy
Releases · ios-control/ios-deploy
Bug fix, unify error reporting
Bug fix for #129 - ios-deploy -c never returns
Added --uninstall_only, --mkdir, --rm options
New "exists" feature, lldb bug fixes.
Thanks to our contributors @urklc and @dot-asm!
from @urklc:
- (-e, --exists) check if the app with given bundle_id is installed or not
from @dot-asm:
- allow to pass command line arguments from (lldb) prompt;
- make lldb exit as opposite to relying on kill (which is problematics
because it messes up tty settings); - handle event timeout in autoexit_command to avoid endless loop;
- use dynamic TCP port and listen on localhost (no need to expose the
port to Internet); - close accept socket once connection is established;
Bug fixes
Bug fix for 1.3.1 :/
Re-fixes #80 --detect not showing non-zero exit code when no devices are detected (--debug is implicit when you set --detect to prevent SIGSEGV
Bug fix
Bug fixes
Thanks to @senthilmanick, @eddieh and @CSOscarTanner for contributing to this release.
- added --download option
- when the device is locked, the python source prints and exists. The server sees this as an empty packet. We are using this to exit out of the connection
- when we use --justlaunch, we need to do safequit and detach. Otherwise we could hang forever
- fixed problem with the parser of the value of the parameter -i
- fix for mismatched SDK build numbers
- allow the symbols and the disk images to be in different DeviceSupport directories.
- fixed python script for lldb launch
- fixed #37 AMDeviceValidatePairing fails when uninstalling
- fixed #74 SIGSEGV-ed while listing the sandbox of an application on iOS8
Xcode 6 Fixes
- Fix lldb status checking
- Fix AFCFileRef[Read|Write] prototypes
Incorrect AFCFileRefRead prototype was causing crashes in 64-bit build when reading large files. - Handle no --args
When no --args are passed application was started with {args} as argument instead of no argument. - Fix usage semantic and pair of resource leaks
AFCConnectionOpen and AFCFIleInfoOpen don't require initialized pointer to pointer to result, but do require corresponding Close calls. - Arrange callback in read_dir for future use
Custom callback is called for every file or directory listed on device. This will be used for file download.