[unai]

I can’t test that right now, but it does work with my personal phone with the same setup.

[unai]

Any updated on this?

[support-michael]

Yes I had a brain fart and it just dawned on me. It appears you are using a newer version of Chrome that has removed the experimental Object.observe() function. The current production version of Chrome v49 includes the observe() function. But Chrome Canary v52 no longer includes this function. The version of Chrome dev tools being loaded to support your device has not been updated yet to work without the observe() function. I suspect that if you use Chrome v49 or older that this problem will not occur.
I missed this earlier as I ran a quick experiment on Canary but using one of my devices that works with Canary chrome dev tools. Thanks for sharing the screenshots of console errors. The problem was right in front of me.

Here’s a bit of info on the Object.observe() function:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/observe
and
http://www.infoq.com/news/2015/11/object-observe-withdrawn

[antons]

I got same error, is there any solution?
I’m using chrome Version 50.0.2661.94 m

[antons]

solved it by installing chromium v. 49 and configuring gapdebug to use it, instead of downgrading chrome

[support-michael]

@antons
After more research on this issue I found the cause of the problem. Here is a note I just posted on working around the issue until we have an update with a fix:
https://www.genuitec.com/forums/topic/android-debug-whitescreen-workaround/

[mirkomen77]

same problem here, using Chrome (regular) 50.0.2661.94 (64bit) OSX

[mirkomen77]

How would you do that?

Thanks

[Author]

Posts