Closed Einstein2150 closed 3 years ago
I'll be honest I have no idea why this happens and I don't have the time to investigate it. It was working fine for all of the beta versions. Somehow lockdownd_start_service
does not seem to work in some cases. Even with the latest libimobiledevice beta it fails. It is working fine when using the libimobiledevice
ideviceimagemounter
tool, which is strange because I use the same source code.
What you can do as a workaround is:
Alternatively you can use the ideviceimagemounter
to upload the DeveloperDiskImage.
I compiled and installed the idevicelocation-Library like under the alternative one (https://github.com/watanabetoshinori/LocationSimulator). Now your and the LocationSimulator from watanebetoshinori is working. I additionally reconnected the device and tried a manual idevicelocation 0 0
in the terminal because there was another error popping up. Crazy 🤪
idevicelocation is included in libimobiledevice since version 1.3.0. You don't have to compile it manually. It will install if you run: brew install libimobiledevice
It will work fine, until you reboot your iOS device (and maybe your mac ?). This will unmount the DeveloperDiskImage. The problem is just with uploading the DeveloperDiskImage to the device.
I think I found the error. Should be fixed now. Hopefully this doesn't break support for older iOS versions.
Console is writing:
[INFO]: Uploading /Users/a1121460/Library/Application Support/LocationSimulator/14.0/DeveloperDiskImage.dmg [ERROR]: mount_image returned -256
Corresponding Image incl. signature-file was manually loaded in the application Support directory
Device is at 14.0 GM