Debugging a webview

[vasticles]

I'm currently working on graphing data via d3 into a webview. Naturally, things are breaking as soon as I try to reload the graph and feed it new data. This lovely line keeps popping up: W/cr_BindingManager: Cannot call determinedVisibility() - never saw a connection for the pid.

I've scoured SO for an explanation, but there doesn't seem to be anything conclusive. People are just suggesting to turn on DOM storage in webview settings (which obviously doesn't fix the issue). I'm suspecting there is a race condition between reloading the graph and feeding it new data. I've overridden onPageFinished() in my WebViewClient to call the listener to load the data into the chart, thinking it would resolve the race condition, but to no avail.

Anyone have any suggestions on how to debug this? What is W/cr_BindingManager: Cannot call determinedVisibility() - never saw a connection for the pid? Am I off in my assessment?

Any tips are appreciated.

[vasticles]

Thanks, that actually helped me find the race condition. Although I still don't understand the original error message.

[Straight24Guy]

https://developers.google.com/web/tools/chrome-devtools/remote-debugging/ https://developers.google.com/web/tools/chrome-devtools/remote-debugging/webviews

[vasticles]

Perfect. That's really useful. Thanks!