Demyan Kimitsa

`pymobiledevice3` is not considered as alternative. the idea is to have same ecosystem solution (e.g. java) under own control. currently I'm porting `pymobiledevice3` project into kotlin, to use as `ilibmobiledevice`...

@yahel-ck thanks for reporting. hadn't tried it on 16.4.1 probably it is related, will check probably tomorrow. any chance you can try older iOS version ? (just to check) also,...

it indeed failed for me on 16.4.1 first time after device is freshly booted. Second and following launches are successful. investigating into.

there is an update to logic in https://github.com/MobiVM/robovm/pull/726 mostly it will provide better error messages and retry logic and cover cases related to development image mounting and LOCKDOWN_E_PAIRING_DIALOG_RESPONSE_PENDING mentioned above....

@yahel-ck its available in snapshot build. can be obtained from there https://mobivm.github.io/dev/

another related case fixed: https://github.com/MobiVM/robovm/pull/734 in recent libmobiledevice *SSL_ERROR -- its common error when communication fails. E.g. it doesn't have specific meaning. I played with iphone8 + ios16.5 and was...

also there once was case met when robovm sees no device while Xcode and other tools were working. It was cause by "usbmuxd is not running" error inside libmobiledevice. restart...

@KristjanP94 thanks, `SSL_ERROR` is verbose error, in your case it should be "Disconnected". But also it would good to receive any java stack trace logs that are piped to console....

@sdringo9 DEBUGSERVER_E_SSL_ERROR -- means that connection to device is terminated. Most likely this happens as your application is crashed. Check Xcode logs. As for LOCKDOWN_E_MUX_ERROR -- its known issue being...

hi, thanks for reporting there is a bug in bindings, will be fixed during ios17 binding update (don't close this issue). meanwhile please use folloiwing workaround. call this line somewhere...