chrome inspector, remote debugging no longer works properly on my mobile app
I have built a progressive web app using Cordova/Ionic. I have been using dev-tools to troubleshoot and analyze my apps inner workings for the better part of 3 years now. In the last few weeks however, i think since Chrome updated to v70+, dev-tools can no longer properly connect and/or manage the app running on my external device (several different test phones).
I have 4 Android test phones, and the same or almost the same issues are happening with dev-tools when connected to each device.
desktop keyboard and mouse do not work anymore - I can't use either to interact with the app on the phone anymore. As well, on some
phones I can't use the element inspector (while on others that does
work). But regardless of phone, I can't use the desktop mouse to
click on app buttons in the web-view. Keyboard does not work on any
of the devices either.
Often, even the native buttons in the app (directly on the phone) won't work if dev-tools has been opened to look at the app. If they
do work, you press the button and like 10-15 seconds later the app
finally responds.
When dev-tools is opened and connected to the device app, the response time of the apps is now extremely slow as well. Sometimes
the app just crashes or I get messages saying "app not responding,
wait or close?"
If I disconnect the phones from the desktop, and/or don't run dev-tools on the app, the app works and responds just fine. Something
specific to dev-tools is causing all these problems.
The different phones have versions 5.1, 6.1.1 and 7.1 running on them for testing purposes. Again, dev-tools worked just fine until a few weeks ago. I recall various small issues impacting performance and web-view rendering in dev-tools, and now all of the above is impacting my ability to troubleshoot and analyze my app (developing).
My environment:
Cordova CLI: 8.0.0
cordova-android: 7.1.1
Gulp version: CLI version 3.9.1
Gulp local:
Ionic Version: 1.3.4
Ionic CLI Version: 1.7.14
Ionic App Lib Version: 0.7.0
OS: Windows 7 SP1
Node Version: v6.10.3
Chrome: Version 70.0.3538.102 (Official Build) (64-bit)
I can't be certain, but I think all these issues began with Chrome updated itself to v70.+ On a side note, my app uses the "webview-plus" plugin....its an older plugin that enables certain inspection features and UI rendering. I removed it to see if maybe it was conflicting with dev-tools, but all the same problems still persisted.
android cordova ionic-framework android-webview 
google-chrome-devtools asked Nov 13 '18 at 14:29
rolingerrolinger
9461423
add a comment |
I have built a progressive web app using Cordova/Ionic. I have been using dev-tools to troubleshoot and analyze my apps inner workings for the better part of 3 years now. In the last few weeks however, i think since Chrome updated to v70+, dev-tools can no longer properly connect and/or manage the app running on my external device (several different test phones).
I have 4 Android test phones, and the same or almost the same issues are happening with dev-tools when connected to each device.
desktop keyboard and mouse do not work anymore - I can't use either to interact with the app on the phone anymore. As well, on some
phones I can't use the element inspector (while on others that does
work). But regardless of phone, I can't use the desktop mouse to
click on app buttons in the web-view. Keyboard does not work on any
of the devices either.
Often, even the native buttons in the app (directly on the phone) won't work if dev-tools has been opened to look at the app. If they
do work, you press the button and like 10-15 seconds later the app
finally responds.
When dev-tools is opened and connected to the device app, the response time of the apps is now extremely slow as well. Sometimes
the app just crashes or I get messages saying "app not responding,
wait or close?"
If I disconnect the phones from the desktop, and/or don't run dev-tools on the app, the app works and responds just fine. Something
specific to dev-tools is causing all these problems.
The different phones have versions 5.1, 6.1.1 and 7.1 running on them for testing purposes. Again, dev-tools worked just fine until a few weeks ago. I recall various small issues impacting performance and web-view rendering in dev-tools, and now all of the above is impacting my ability to troubleshoot and analyze my app (developing).
My environment:
Cordova CLI: 8.0.0
cordova-android: 7.1.1
Gulp version: CLI version 3.9.1
Gulp local:
Ionic Version: 1.3.4
Ionic CLI Version: 1.7.14
Ionic App Lib Version: 0.7.0
OS: Windows 7 SP1
Node Version: v6.10.3
Chrome: Version 70.0.3538.102 (Official Build) (64-bit)
I can't be certain, but I think all these issues began with Chrome updated itself to v70.+ On a side note, my app uses the "webview-plus" plugin....its an older plugin that enables certain inspection features and UI rendering. I removed it to see if maybe it was conflicting with dev-tools, but all the same problems still persisted.
android cordova ionic-framework android-webview google-chrome-devtools asked Nov 13 '18 at 14:29
rolingerrolinger
9461423
what exactly do you mean with dev-tools? the feature i am aware of is remote debugging, which seems to work for me...
– Stefan
Nov 13 '18 at 17:47
1
@Stefan - Dev-Tools, Inspector, web-view, remote debugging...in this context, all the same thing:chrome://inspect/#devices- too often people use different names for the same thing.
– rolinger
Nov 13 '18 at 21:42
1
I have the same problem. Did you find a solution? There's no error documented on Ionic/Chrome...
– pete
Nov 30 '18 at 7:44
@pete - no, i haven't found a solution yet. However, it seems to have gotten a little bit better. I still can't interact with the app itself using the desktop keyboard and mouse (type in input fields, click on buttons), but the mouse does work for element inspection. To navigate my app I load it up in Inspector and then have to use the app for button clicks and field input.
– rolinger
Dec 1 '18 at 13:05
add a comment |
I have built a progressive web app using Cordova/Ionic. I have been using dev-tools to troubleshoot and analyze my apps inner workings for the better part of 3 years now. In the last few weeks however, i think since Chrome updated to v70+, dev-tools can no longer properly connect and/or manage the app running on my external device (several different test phones).
I have 4 Android test phones, and the same or almost the same issues are happening with dev-tools when connected to each device.
desktop keyboard and mouse do not work anymore - I can't use either to interact with the app on the phone anymore. As well, on some
phones I can't use the element inspector (while on others that does
work). But regardless of phone, I can't use the desktop mouse to
click on app buttons in the web-view. Keyboard does not work on any
of the devices either.
Often, even the native buttons in the app (directly on the phone) won't work if dev-tools has been opened to look at the app. If they
do work, you press the button and like 10-15 seconds later the app
finally responds.
When dev-tools is opened and connected to the device app, the response time of the apps is now extremely slow as well. Sometimes
the app just crashes or I get messages saying "app not responding,
wait or close?"
If I disconnect the phones from the desktop, and/or don't run dev-tools on the app, the app works and responds just fine. Something
specific to dev-tools is causing all these problems.
The different phones have versions 5.1, 6.1.1 and 7.1 running on them for testing purposes. Again, dev-tools worked just fine until a few weeks ago. I recall various small issues impacting performance and web-view rendering in dev-tools, and now all of the above is impacting my ability to troubleshoot and analyze my app (developing).
My environment:
Cordova CLI: 8.0.0
cordova-android: 7.1.1
Gulp version: CLI version 3.9.1
Gulp local:
Ionic Version: 1.3.4
Ionic CLI Version: 1.7.14
Ionic App Lib Version: 0.7.0
OS: Windows 7 SP1
Node Version: v6.10.3
Chrome: Version 70.0.3538.102 (Official Build) (64-bit)
I can't be certain, but I think all these issues began with Chrome updated itself to v70.+ On a side note, my app uses the "webview-plus" plugin....its an older plugin that enables certain inspection features and UI rendering. I removed it to see if maybe it was conflicting with dev-tools, but all the same problems still persisted.
android cordova ionic-framework android-webview google-chrome-devtools asked Nov 13 '18 at 14:29
rolingerrolinger
9461423
I have built a progressive web app using Cordova/Ionic. I have been using dev-tools to troubleshoot and analyze my apps inner workings for the better part of 3 years now. In the last few weeks however, i think since Chrome updated to v70+, dev-tools can no longer properly connect and/or manage the app running on my external device (several different test phones).
I have 4 Android test phones, and the same or almost the same issues are happening with dev-tools when connected to each device.
desktop keyboard and mouse do not work anymore - I can't use either to interact with the app on the phone anymore. As well, on some
phones I can't use the element inspector (while on others that does
work). But regardless of phone, I can't use the desktop mouse to
click on app buttons in the web-view. Keyboard does not work on any
of the devices either.
Often, even the native buttons in the app (directly on the phone) won't work if dev-tools has been opened to look at the app. If they
do work, you press the button and like 10-15 seconds later the app
finally responds.
When dev-tools is opened and connected to the device app, the response time of the apps is now extremely slow as well. Sometimes
the app just crashes or I get messages saying "app not responding,
wait or close?"
If I disconnect the phones from the desktop, and/or don't run dev-tools on the app, the app works and responds just fine. Something
specific to dev-tools is causing all these problems.
The different phones have versions 5.1, 6.1.1 and 7.1 running on them for testing purposes. Again, dev-tools worked just fine until a few weeks ago. I recall various small issues impacting performance and web-view rendering in dev-tools, and now all of the above is impacting my ability to troubleshoot and analyze my app (developing).
My environment:
Cordova CLI: 8.0.0
cordova-android: 7.1.1
Gulp version: CLI version 3.9.1
Gulp local:
Ionic Version: 1.3.4
Ionic CLI Version: 1.7.14
Ionic App Lib Version: 0.7.0
OS: Windows 7 SP1
Node Version: v6.10.3
Chrome: Version 70.0.3538.102 (Official Build) (64-bit)
I can't be certain, but I think all these issues began with Chrome updated itself to v70.+ On a side note, my app uses the "webview-plus" plugin....its an older plugin that enables certain inspection features and UI rendering. I removed it to see if maybe it was conflicting with dev-tools, but all the same problems still persisted.
android cordova ionic-framework android-webview google-chrome-devtools android cordova ionic-framework android-webview google-chrome-devtools asked Nov 13 '18 at 14:29
rolingerrolinger
9461423
asked Nov 13 '18 at 14:29
rolingerrolinger
9461423
edited Nov 13 '18 at 21:43
rolinger
asked Nov 13 '18 at 14:29
rolingerrolinger
9461423
asked Nov 13 '18 at 14:29
rolingerrolinger
9461423
asked Nov 13 '18 at 14:29
rolingerrolinger
9461423
9461423
what exactly do you mean with dev-tools? the feature i am aware of is remote debugging, which seems to work for me...
– Stefan
Nov 13 '18 at 17:47
1
@Stefan - Dev-Tools, Inspector, web-view, remote debugging...in this context, all the same thing:chrome://inspect/#devices- too often people use different names for the same thing.
– rolinger
Nov 13 '18 at 21:42
1
I have the same problem. Did you find a solution? There's no error documented on Ionic/Chrome...
– pete
Nov 30 '18 at 7:44
@pete - no, i haven't found a solution yet. However, it seems to have gotten a little bit better. I still can't interact with the app itself using the desktop keyboard and mouse (type in input fields, click on buttons), but the mouse does work for element inspection. To navigate my app I load it up in Inspector and then have to use the app for button clicks and field input.
– rolinger
Dec 1 '18 at 13:05
add a comment |
what exactly do you mean with dev-tools? the feature i am aware of is remote debugging, which seems to work for me...
– Stefan
Nov 13 '18 at 17:47
1
@Stefan - Dev-Tools, Inspector, web-view, remote debugging...in this context, all the same thing:chrome://inspect/#devices- too often people use different names for the same thing.
– rolinger
Nov 13 '18 at 21:42
1
I have the same problem. Did you find a solution? There's no error documented on Ionic/Chrome...
– pete
Nov 30 '18 at 7:44
@pete - no, i haven't found a solution yet. However, it seems to have gotten a little bit better. I still can't interact with the app itself using the desktop keyboard and mouse (type in input fields, click on buttons), but the mouse does work for element inspection. To navigate my app I load it up in Inspector and then have to use the app for button clicks and field input.
– rolinger
Dec 1 '18 at 13:05
what exactly do you mean with dev-tools? the feature i am aware of is remote debugging, which seems to work for me...
– Stefan
Nov 13 '18 at 17:47
what exactly do you mean with dev-tools? the feature i am aware of is remote debugging, which seems to work for me...
– Stefan
Nov 13 '18 at 17:47
1
1
@Stefan - Dev-Tools, Inspector, web-view, remote debugging...in this context, all the same thing:
chrome://inspect/#devices - too often people use different names for the same thing.– rolinger
Nov 13 '18 at 21:42
@Stefan - Dev-Tools, Inspector, web-view, remote debugging...in this context, all the same thing:
chrome://inspect/#devices - too often people use different names for the same thing.– rolinger
Nov 13 '18 at 21:42
1
1
I have the same problem. Did you find a solution? There's no error documented on Ionic/Chrome...
– pete
Nov 30 '18 at 7:44
I have the same problem. Did you find a solution? There's no error documented on Ionic/Chrome...
– pete
Nov 30 '18 at 7:44
@pete - no, i haven't found a solution yet. However, it seems to have gotten a little bit better. I still can't interact with the app itself using the desktop keyboard and mouse (type in input fields, click on buttons), but the mouse does work for element inspection. To navigate my app I load it up in Inspector and then have to use the app for button clicks and field input.
– rolinger
Dec 1 '18 at 13:05
@pete - no, i haven't found a solution yet. However, it seems to have gotten a little bit better. I still can't interact with the app itself using the desktop keyboard and mouse (type in input fields, click on buttons), but the mouse does work for element inspection. To navigate my app I load it up in Inspector and then have to use the app for button clicks and field input.
– rolinger
Dec 1 '18 at 13:05
add a comment |
1 Answer
1
active
oldest
votes
I have the same issue, it worked fine some months ago, but it is now broken.
As a workaround, I tried to disable screencast, restart the app and then restart devtools and it worked!
Hope this helps!
answered Dec 18 '18 at 3:43
moppagmoppag
17618
without screen cast, how can you use the desktop keyboard/mouse to interact with the app?
– rolinger
Dec 21 '18 at 14:30
I can't. I just interact with the app directly on the phone. But at least, I can use breakpoints and Network tools.
– moppag
Dec 22 '18 at 20:21
This doesn't get things completely functional again, but certainly very helpful to hit breakpoints again. Thanks!
– BRass
Dec 24 '18 at 15:14
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53283252%2fchrome-inspector-remote-debugging-no-longer-works-properly-on-my-mobile-app%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have the same issue, it worked fine some months ago, but it is now broken.
As a workaround, I tried to disable screencast, restart the app and then restart devtools and it worked!
Hope this helps!
answered Dec 18 '18 at 3:43
moppagmoppag
17618
without screen cast, how can you use the desktop keyboard/mouse to interact with the app?
– rolinger
Dec 21 '18 at 14:30
I can't. I just interact with the app directly on the phone. But at least, I can use breakpoints and Network tools.
– moppag
Dec 22 '18 at 20:21
This doesn't get things completely functional again, but certainly very helpful to hit breakpoints again. Thanks!
– BRass
Dec 24 '18 at 15:14
add a comment |
I have the same issue, it worked fine some months ago, but it is now broken.
As a workaround, I tried to disable screencast, restart the app and then restart devtools and it worked!
Hope this helps!
answered Dec 18 '18 at 3:43
moppagmoppag
17618
without screen cast, how can you use the desktop keyboard/mouse to interact with the app?
– rolinger
Dec 21 '18 at 14:30
I can't. I just interact with the app directly on the phone. But at least, I can use breakpoints and Network tools.
– moppag
Dec 22 '18 at 20:21
This doesn't get things completely functional again, but certainly very helpful to hit breakpoints again. Thanks!
– BRass
Dec 24 '18 at 15:14
add a comment |
I have the same issue, it worked fine some months ago, but it is now broken.
As a workaround, I tried to disable screencast, restart the app and then restart devtools and it worked!
Hope this helps!
answered Dec 18 '18 at 3:43
moppagmoppag
17618
I have the same issue, it worked fine some months ago, but it is now broken.
As a workaround, I tried to disable screencast, restart the app and then restart devtools and it worked!
Hope this helps!
answered Dec 18 '18 at 3:43
moppagmoppag
17618
answered Dec 18 '18 at 3:43
moppagmoppag
17618
answered Dec 18 '18 at 3:43
moppagmoppag
17618
answered Dec 18 '18 at 3:43
moppagmoppag
17618
17618
without screen cast, how can you use the desktop keyboard/mouse to interact with the app?
– rolinger
Dec 21 '18 at 14:30
I can't. I just interact with the app directly on the phone. But at least, I can use breakpoints and Network tools.
– moppag
Dec 22 '18 at 20:21
This doesn't get things completely functional again, but certainly very helpful to hit breakpoints again. Thanks!
– BRass
Dec 24 '18 at 15:14
add a comment |
without screen cast, how can you use the desktop keyboard/mouse to interact with the app?
– rolinger
Dec 21 '18 at 14:30
I can't. I just interact with the app directly on the phone. But at least, I can use breakpoints and Network tools.
– moppag
Dec 22 '18 at 20:21
This doesn't get things completely functional again, but certainly very helpful to hit breakpoints again. Thanks!
– BRass
Dec 24 '18 at 15:14
without screen cast, how can you use the desktop keyboard/mouse to interact with the app?
– rolinger
Dec 21 '18 at 14:30
without screen cast, how can you use the desktop keyboard/mouse to interact with the app?
– rolinger
Dec 21 '18 at 14:30
I can't. I just interact with the app directly on the phone. But at least, I can use breakpoints and Network tools.
– moppag
Dec 22 '18 at 20:21
I can't. I just interact with the app directly on the phone. But at least, I can use breakpoints and Network tools.
– moppag
Dec 22 '18 at 20:21
This doesn't get things completely functional again, but certainly very helpful to hit breakpoints again. Thanks!
– BRass
Dec 24 '18 at 15:14
This doesn't get things completely functional again, but certainly very helpful to hit breakpoints again. Thanks!
– BRass
Dec 24 '18 at 15:14
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53283252%2fchrome-inspector-remote-debugging-no-longer-works-properly-on-my-mobile-app%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
what exactly do you mean with dev-tools? the feature i am aware of is remote debugging, which seems to work for me...
– Stefan
Nov 13 '18 at 17:47
1
@Stefan - Dev-Tools, Inspector, web-view, remote debugging...in this context, all the same thing:
chrome://inspect/#devices- too often people use different names for the same thing.– rolinger
Nov 13 '18 at 21:42
1
I have the same problem. Did you find a solution? There's no error documented on Ionic/Chrome...
– pete
Nov 30 '18 at 7:44
@pete - no, i haven't found a solution yet. However, it seems to have gotten a little bit better. I still can't interact with the app itself using the desktop keyboard and mouse (type in input fields, click on buttons), but the mouse does work for element inspection. To navigate my app I load it up in Inspector and then have to use the app for button clicks and field input.
– rolinger
Dec 1 '18 at 13:05