Josef Micka

``` ErrorCode 3: Failed to create snapshot: File exists (17) at path "/private/var" (MBErrorDomain/3) ``` this error is from device itself, and is caused by remnants of unfinished backup/restore ......

yes, you do have access to syslog, if you can run idevicebackup2, you can also run idevicesyslog in one terminal session run ``` idevicesyslog ``` in other terminal session, run...

mind, you might want to compile it as static, and then dllexport/import will cause issues on windows compiler for visual studio i use _WINDLL as attribute for dynamic (dll) target...

if rvi doesn't work with latest usbmux, it means rvi needs to be upgraded

@xanadu-lee i don't think so ... there is fork that uses avahi for searching network with bonjour, fork is located here https://github.com/tihmstar/usbmuxd2

@jkcoxson i see, i didn't check code, so i did assume it's fork, because of name ... thanks for info.

@xanadu-lee depending on device, it might refuse connection if you open session to it too offten. you can keep lockdown connection (session) open for extended period of time, and start...

AFC is exception, after device is connected, you start it once, then keep it open ... but you can disconnect lockdown, after you get hold of AFC connection. other services,...

considering stack trace, that leads to thread management library inside kernel, it might not be related to libimobile another possibility is, that you overwrite or release pointer you sent inside...

usage print without error means unrecongnized input parameter, i expect some typo in UDID (some other character than hexadeciemal numbers) that causes it to treat it as multiple entities instead...