-
Notifications
You must be signed in to change notification settings - Fork 470
Unable to connect to iPhone even when "Web Inspector = ON" in iOS 13 Beta #314
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
The way how web inspector initiates the service on device and the way how it should mange conversations (WIR messages) is changed on iOS 13 Beta ... (hint: related to the SSL flag on the service connection). |
Have any update for this issue? I have got the same issue |
Pull request [ ios 13 support changes - Perfecto contribution ] has been created. |
any update on when this will be done? |
hello, do we have any update? |
Can Apple just go bankrupt so we don't have to deal with this shit anymore? |
I got the same issue on iOS 13.1.1 with Appium 1.15.0-1. However, it works fine on iOS 11.4.1 and iOS 12.4.1 with this version of Appium. |
Appium 1.15 does not use this.
…On Sun, Oct 6, 2019 at 5:47 AM nhhphuong ***@***.***> wrote:
I got the same issue on iOS 13.1.1 with Appium 1.15.0-1
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#314?email_source=notifications&email_token=AAT6IUTAEYVIRVK2JCWONBDQNHM5VA5CNFSM4HTW5TAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAOJIXY#issuecomment-538743903>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAT6IUWCOUF22HDYMB3DP4DQNHM5VANCNFSM4HTW5TAA>
.
|
For me, with same iPhone iOS 13.0, it only working with macOS 10.14.6 and not working with macOS 10.15.
|
I have similar problem with connection to iPhone with iOS 13.1.2. But in my case there is not a problem with ssl I think, but Web Inspector is ON.. ss.add_server_fd(496) |
you could try |
But what about Windows 10? As I understand this solution is for OS X? |
windows binaries will be available later, you could build with mingw |
I failed to build with mingw, but I need to debug mobile safari on Windows PC. So could you build it please? |
Thanks @imurchie, it works fine with Appium 1.15.0-1 and iOS 13.0 simulator (I don't have a real device with iOS 13.0). However, I got a problem with real device run on iOS 13.1.2. It can open safari and open web app, but it cannot execute sendKeys or click on that page. About a native app run on real device with iOS 13.1.2, it works fine. |
Is there an ETA on windows binaries? |
我觉得不是数据线问题,我用品胜数据线,可以正常连到macmini,然后Chrome或者Safari也可以正常去debug iphone6s。但是同样的数据线,用这个工具在Windows下就不能连。 |
I am having this issue on
We inspector is ON, I tried restarting both devices, pluging and unpluging, reinstalling Is there any working advice? |
@Xquick check out readme, you need to have libimobiledevice 1.2.1, which is only available from sources |
When ios-webkit-debug-proxy binary for ios 13 will be created for windows? |
@mkhrystenko there's no ETA, you can easily do it yourself |
@artygus where I can find instructions how to compile ios-webkit-debug-proxy with gcc? |
unfortunately there're no guides and no plans to do them, it's nothing specific to this project, just general familiriaty win mingw, similar question were raised a couple of times in libimobiledevice issues, you could start from here |
I am trying to use compile the Windows binaries myself and have submitted this issue since I am stuck : #351 |
I had to resort to using weinre with an ngrok hack for accessing the host on ssl. Its dodgy and slow. It seems IOS 13 has completely uprooted many things. They even changed the device name breaking device detection. This is standard. I'm still going with work arounds for IOS 13. You can try this work around for now I gave up trying the direct remote debug.
|
If you go weinre, be ready for despair. It wont log everything and is slow. I am still trying to get IOS 13 device detection working as its changed and broken everything. |
new release is out https://github.com/google/ios-webkit-debug-proxy/releases/tag/v1.8.6, with iOS 13 support |
target appears but it's blank. No output. Running this binary standalone. |
@danrossi dev tools page is blank or utility doesn't find pages/devices? |
the dev tools console. refreshed multiple times and nothing. The device showed up. and it connected to it immediately in powershell
|
I got to this location and a different console output. But it's still empty
|
Thanks. Now connected. |
I changed the command to this
load navigate to it. http://localhost:9222/ copy and paste this url and navigate to it devtools://devtools/bundled/inspector.html?ws=localhost:9222/devtools/page/4 It's a different screen, its not a html console its a native chrome console, and blank. Refreshing shows no output. |
I checked this readme already, and checked it again and many times.
installed this version: ios-webkit-debug-proxy: 1.8.6 Next this: installed: [email protected] Then I run this: Result: Then I connected the phone, and I see this error in console multiple times:
I go to URL in google chrome: chrome://inspect/#devices I see titles of web sites, opened in Safari, And click inspect on one of them. Opened new blank window of devtools, and i see in console this:
What I am doing wrong? |
@Pavel-DV I think you should post your issue at the relevant repo UPD: blank dev tools might be fixed in RemoteDebug/remotedebug-ios-webkit-adapter#186 |
If all this bugs are inside remotedebug-ios-webkit-adapter, I tried to use ios-webkit-debug-proxy without it.
I navigated to http://localhost:9222/ It is opened DevTools-like interface, but without html elements of web page in the iPhone. |
@Pavel-DV iwdp is a tool that allows you to send commands to webinspectord via websocket interface, it won't work with chrome devtools frontend without compatibility adapter since chrome and safari devtools protocols diverted long ago quote from readme
|
I thought that since it’s written in readme, this way should work. I thought that the interface that opens through that link is another devtool, specially converted for this protocol. I think the readme is confusing for many people who have done the same thing as me.
I tried this:
So, ideviceinfo exists. I don't know if it is works correctly. |
@Pavel-DV obviously it doesn't work, there's clearly an error output. it seems https://www.npmjs.com/package/vs-libimobile is an ancient package, remotedebug-ios-webkit-adapter needs another way to read device version
you're more than welcome to contribute a proper wording |
@Pavel-DV new version of remotedebug-ios-webkit-adapter is out with RemoteDebug/remotedebug-ios-webkit-adapter#188 and RemoteDebug/remotedebug-ios-webkit-adapter#186 merged your issues should've been solved |
@artygus Thanks! Now all works for me. |
there is no release file for this. has it been updated yet ? I got 1.8.6 by mistake again |
Windows 10 - command prompt says i'm connected to the iPhone |
You have to wait for a new binary release. 1.8.6 has the bug. I gave up , and had to suffer with weinre SSL hacks through ngrok. Slow but coped. |
latest fix is not released. any ideas ? cant even test it works. blank console 100% |
This is silly. How can we build a 1.8.7 binary for Windows ? Still no chance to get a fix. |
I am having this issue on iOS 13.3 against macOS 10.15.4 ios_webkit_debug_proxy 1.8.6 Web inspector is ON, I tried restarting both devices, pluging and unpluging, reinstalling Any work around for the same? |
Was trying to use ios-webkit-debug-proxy to connect to latest iOS 13 Beta on iPhone 8.
After running the command:
Output:
Unable to connect to iPhone (10e43da25a9174d34a07a9287c5d709f878xxxxx)
Please verify that Settings > Safari > Advanced > Web Inspector = ON
Even though I can confirm that the option is set to ON, still the error persists.
When running an appium session, I get an error because of the same reason
An unknown server-side error occurred while processing the command. Original error: Could not start ios_webkit_debug_proxy server: Timed out waiting for ios_webkit_debug_proxy to open (Selenium::WebDriver::Error::UnknownError)
The text was updated successfully, but these errors were encountered: