-
Notifications
You must be signed in to change notification settings - Fork 470
No connection with iOS 15.1 #383
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
I tried to debug it a bit further, but I am not experienced with neither OpenSSL debugging nor the Apple protocols and usbmuxd. Here are some more information. I added debug output to
Output when running this modified version:
The ssl session seemes to be open. Only the verify return code of 21 seemse odd. Maybe the SSL Certificates are not correct? So I also printed the I guess from here it would need more detailed knowledge of the systems to debug any further. |
hi @everlanes, I faced the same issue. do you have any progress? It recurred to me that when upgrading to iOS13 similar issue happens(#314)? Just my humble guess, is there possibility that could be rendering issue? |
Sorry, no progress. I gave up on this and used inspect.dev for my current problem instead. |
hi @everlanes, |
Running into the same issue - using inspect.dev now, which only works with Safari |
Ios 14.8.1 has the exact same problem |
This issue keeps happening, Inspect somehow works and was working fine but is now paid. And it does not warrant paying for something I use once or twice a year to debug errors. Is there anything else that works ? |
same issue |
working on this to get rid of dependency of libimobiledevice's openssl |
checkout the https://github.com/google/ios-webkit-debug-proxy/releases/tag/v1.9.0 please |
This works now on Linux Mint. I can connect to an iPhone with iOS 16.3.1. |
I want to debug a webpage on Apple iPhone XR with iOS 15.1
I compiled all libimobiledevice dependencies using the GIT repositories with latest commits.
When I start the ios_webkit_debug_proxy I get the following error messages:
Any chance that this might work?
Versions:
The text was updated successfully, but these errors were encountered: