-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
'ios launch' unable to launch app #54
Comments
Hey there, please run it with the |
|
Can you maybe:
|
btw i has to use sudo to run dproxy and launch, or terminal will say
hope it dosen't matter, |
yeah you can also temporarily chmod /var/run so your user has access. I should add that to the error message |
Is your cable broken or something? :-D |
I was able to repro the issue using |
My current estimation is that this occurs when the device itself is, to use a technical term, "borked". (Perhaps some phone-internal service has crashed/hung). I have this occurring on an iPhone 8 running 15.0.1. Host is Ubuntu LTS, so this isn't an Xcode interaction. 20 other devices are connected concurrently on the same machine, and are stable and respond to go-ios commands, so it's not inherently usbmuxd related (unless usbmuxd can leak per-device resources?). tidevice commands for "ps" and "launch" also fail on this device, so it's not go-ios implementation specific. Device started off working and launching processes, and communication continues to the device over existing go-ios tunnels in spite of the inability to launch new processes via go-ios. Appear to be able to launch new tunnels, and other functionality works. Agreeing with comments above, impacted commands are minimally "ps", "kill", and "launch", leaving me to suspect that a reboot is probably the only recourse for recovery. |
Hello, i try to use go-ios v1.0.24 to launch apps on my iphone, but it failed.
i tried other commands like
ios screenshot/apps/info/syslog
work,
ios ps & kill
not workmy phone & sysver: iphone11 pro max ios14.3
here is my log output:
The text was updated successfully, but these errors were encountered: