-
Notifications
You must be signed in to change notification settings - Fork 470
The tool doesn't work with ios 11 #208
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
Comments
When connecting the device to El Capitan. Safari also cannot see the device. |
If safari can not see the device iwdp won't be able to see it either |
Can not see on EL Capital. On Sierra it should work. I didn't upgrade my mini mac yet. |
I'm on El Captain and I'm able to see the devices. If you start simulator does safari pick it? |
You are able to see ios11 devices? I'm talking about ios11. On Sierra the device with ios11 appear in develop tab of safari for a 1 second and disappear. |
I don't know how to run ios11 simulator. Maybe I need Xcode 9. |
@ViktorGal oh I see now, didn't notice ios11 in issue's tittle, I didn't upgrade to Sierra just yet, will do later this week. I'll let you know if I have any progress |
Thanks @artygus. Need to upgrade to High Sierra beta for ios 11. |
Newest chrome preview works with ios 11, even in sierra. The proxy does not though. |
@tobsch do you mean that default dev tools front-end doesn't work? |
yep! it only works with the newest safari preview |
Default dev tools url is super old, but even latest dev tools are quite useless because safari/chrome protocols are quite different now, I'd recommend using adapter. You can find some info in readme https://github.com/google/ios-webkit-debug-proxy#using-with-devtools |
On El Captain call to libimobiledevice method UPD: after applying patch to libimobiledevice, handshake happens, but device gets disconnected later |
Latest stable Safari on Sierra gives the same result, device appears and disappears in a moment. The tool also reports disconnect with applied patch to libimobiledevice I mentioned above . |
We tried to run compile the code over ios11-supporting-libimobiledevice (== the device is identified and libimobiledevice commands are working) and ios-webkit-debug-proxy still failing... |
I am getting the below error while executing the below command on iOS 11 Beta device with XCode 8.3.3. Error: Can any one please help in this regard. |
I was able to resolve the issue by cloning the libimobiledevice project from GitHub and then implementing the patch mentioned in below URL:- |
@artygus ios-debug-webkit-proxy version: 1.7.1 |
hi @AnuKadloor at this point utility doesn't support iOS 11. Even latest Safari on Sierra doesn't allow you to inspect pages of iOS 11 devices. However, on High Sierra I was able to inspect devices with iOS 11. I suspect there're certain changes in usbmuxd protocol, the issue needs further investigation. |
Thanks for the quick reply @artygus PS: I'm able to inspect pages of iOS 11 devices on my Mac Sierra 10.12.6 with Safari 11.0 |
oh cool, Safari 11 Beta was only available on High Sierra, look's stable works even on El Captain. I can't make any promises, any help in investigation would be greatly appreciated 🙂 UPD: I was able to install Safari Beta 3 on El Captain |
👍 |
Hey...any updates on this issue? |
@AnuKadloor yes, looks like ios 11 doesn't support partial plist's, I'm thinking about workaround atm |
Hei guys, any updates on this issue? Many thanks! |
@AnuKadloor @fabianaapateanu please check out the ios11_support branch. You still need to apply patch to libimobiledevice or device handshake would fail, see comment above for details |
Thanks for the fix @artygus. |
@artygus i installed the branch you created for the iOS 11 fix and it seems to be working fine. |
@mayureshshirodkar I've just merged the branch to master, I think I'll keep the issue open until libimobiledevice/libimobiledevice#510 is resolved |
@artygus I will test tomorrow, I just received a Macbook and iPhone on which I can install all the betas :) will come back with feedback. thanks! |
pairing patch made it's way into libimobiledevice's master libimobiledevice/libimobiledevice@5a85432 |
brew update resolved issue for me |
I agree with @Vadim-Kovrizhkin. I followed his steps, and it worked. |
After
....bplist00..._
..WIRFinalMessageKeyO..
bplist00.....Z
_selector..rpc_reportIdentifier:Z
__argument.....WIRConnectionIdentifierKey
_.#6977420-6980-418f- b735-51a3692d2806 .1<?\
message sent.
Device closes connection.
The text was updated successfully, but these errors were encountered: