[
https://issues.apache.org/jira/browse/CB-11158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258932#comment-15258932
]
Jimmy Thomson commented on CB-11158:
------------------------------------
Create a cordova project (I used 5.4.1) and copy the index.html and index.js
files from the repro.zip into the appropriate locations in the project. Add
cordova-plugin-inappbrowser (tested using 1.2.0) to the project.
Build and run on android, I used the VS Android Emulator running on android 4.4.
Run the app, and attach to it with a debugger. Set breakpoints on the two lines
in index.js around iab.executescript, that is lines 36 and 38.
Click the button in the app, and it will open a page. The first breakpoint
should get hit when the page opens. Resume running, and then the bug triggers.
Using Chrome to debug the webview will seem to indicate that the breakpoint is
not hit, although it will move the text cursor to the start of the line with
the breakpoint. No more interaction via the console or breakpoints is possible.
If you use VS to debug the webview, it will appear to stop on the second
breakpoint, but attempting to use the JS console will fail, and you get no
mouseover information or anything.
It seems that this sequence of events causes the webview to report an internal
error to all debugging requests. If you do NOT set the second breakpoint, then
debugging continues to work as expected, and clicking the button a second time
will result in the first breakpoint being hit again successfully.
> Debugging with inappbrowser can result in a broken webview debugger
> -------------------------------------------------------------------
>
> Key: CB-11158
> URL: https://issues.apache.org/jira/browse/CB-11158
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin InAppBrowser
> Affects Versions: 1.2.0
> Environment: Android 4.4
> Reporter: Jimmy Thomson
> Priority: Minor
> Attachments: repro.zip
>
>
> When attempting to debug a callback in inappbrowser, I found that a
> particular sequence of events would result in the webview no longer
> responding to the debugger. The app itself appears to work, but neither
> chrome nor visual studio are able to debug the app.
> I am going to upload a repro file and give steps relative to the file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
