-
Notifications
You must be signed in to change notification settings - Fork 261
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
ideviceinstaller -l & -i failed with "Could not connect to lockdownd. Exiting." #122
Comments
难道不是因为手机没解锁? |
从表现来说不可能。不至于蠢成这样来提issue…… |
I also met the issue: "Could not connect to lockdownd. Exiting." Environment Xcode 11 Could not connect to lockdownd. Exiting. |
also got the same issue |
same issue, |
I got ideviceinstaller -l to work on Mac 10.15.7. It's not pretty but here's what I had to do:
|
I don't know what you are doing |
I'm running the latest libimobiledevice (v1.3.0). Good to know that this is not expected behavior. Maybe it's just something fluky with my setup. Unfortunately turning off SIP and chmod was the only way I could get rid of the lockdown error. |
I met with "Could not connect to lockdownd. Exiting." when I used
ideviceinstaller -l
orideviceinstaller -i xxx.ipa
。Environment
Mac OS : 10.15
iOS Devices:iPhone XR(13.0),iPhone Xs Max(12.3)
Software:
Description
$ ideviceinstaller -l
Could not connect to lockdownd. Exiting.
$ ideviceinstaller -d -l
...
11:34:04 idevice.c:387 internal_connection_receive_timeout(): ERROR: usbmuxd_recv_timeout returned -35 (Resource temporarily unavailable)
...
idevice_info & idevicescreenshot works well.
P.S
for ideviceinstaller -l and -i command
macos 10.14.5 & iPhone 7(iOS 12.1.3)works well
macos 10.14.6 & iPhone 8(iOS 11.4.1)did not work
macos 10.15 & iPhone 6(iOS 10.3.3)works well only if I execute 'sudo chmod -R 777 /var/db/lockdown/ '
I think maybe the new OS version of mac leads to the result。
The text was updated successfully, but these errors were encountered: