-
Notifications
You must be signed in to change notification settings - Fork 354
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
usbmuxd logging asyncReadComplete, message was too large (65536 bytes, max = 65535) while using usbipd-win #247
Comments
Why don't you install Apple's AppleMobileDeviceSupport package (part of iTunes installer)? It comes with the official usbmuxd and then you don't have to compile the open source usbmuxd. |
But usbmuxd runs on the WSL side under Linux? How does it work if the usbmuxd is under Windows? |
I have no idea, it has an open socket 27015, you can try if you can connect. Apart from that you can build libimobiledevice and tools for Windows using msys2. |
I did try to build using mysys2 but it failed in linking stage even though I had build everything correctly or so I thought. Is there correct build instruction for mysys2 anywhere? I got this error when building libimobiledevice and I couldn't see what I was missing...
|
Hi all
I'm trying to run
idevicerestore --erase --latest
on WSL using the usbipd-win project but I'm getting the following error logged in syslog on WSL.In my setup I have an iPhone bound and attached to WSL from Window and the idevicerestore is failing once it starts to transfer data to the device.
I have also noticed this same error if we try to sideload and app to an iOS device.
Seems there is an issue with message sizes while transferring via usbip. Any possibility somebody could look into this who understands the flow?
The issue was raised with the usbipd-win project here but they guys there seem to think this may be a usbmuxd problem. Thanks to anyone who has time to look at this.
Donie
The text was updated successfully, but these errors were encountered: