-
Notifications
You must be signed in to change notification settings - Fork 67
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
[cordova-debug-adapter] Error: Unable to find web view #54
Comments
The port specified in launch.json (when targeting iOS) is supposed to be a currently-unused port that we can create a new instance of ios-webkit-debug-proxy on. ios-webkit-debug-proxy then listens on additional ports (such as 9222) for different devices and simulators that it connects to. The reason that you couldn't see anything on port 9221 is we changed the default port away from 9221 since it might be in use for other reasons (it's the default chrome-debugging port), so you would need to check on port 9220, and we also clean up ios-webkit-debug-proxy when we stop debugging. To try and troubleshoot your problem, could you please do the following:
|
Thanks for your detailed reply!
The returned URLs made me think a little bit. My app name (the If I remember right, Now I am using the simple app name, and I am searching for a way to change the display name. |
The space should work fine (we url encode the name to account for that) but I don't believe that ampersands are permitted since they turn up in places like the above and cause trouble. In this case we were expecting the ampersand to be encoded to "%26" in the url, but that doesn't seem to be the case, so we didn't detect the app as yours. |
On my Mac, I am able to execute
cordova build
orcordova run
without problems. But when it comes to debugging, I always get the errorIn the debug console, the last output is
According to the documentation of
ios_webkit_debug_proxy
, I should see the connected devices on http://localhost:9221. But this page can be displayed only, when I startios_webkit_debug_proxy
manually in the terminal:But when I try debugging, I still get the same error.
The configuration in my
launch.json
isI was wondering, that here the port is 9220, but the proxy tells something with 9222. Therefore I changed the port in
launch.json
, too. But this produces only another error:I am using the following versions:
The text was updated successfully, but these errors were encountered: