|
|
Post by jontara on May 23, 2017 5:54:26 GMT
I once had this working. I can't seem to get it to work now. What is the secret sauce?
I am able to remote inspect Chrome, but not my Rhodes app.
In case it matters, it's on a Samsung SM-T813 Galaxy Tab S3 running Android 7.0.
I previously had this working on an SM-T230NU with Android 4.4.2. (It's the first version that supports this.)
I have debug capability set in build.yml.
I recall maybe I have to set something in AndroidManifest.erb? But i see AndroidManifest.erb gets value from build.yml debug capability, right?
|
|
|
|
Post by jontara on May 23, 2017 6:11:03 GMT
I got it to work with GenyMotion, but not on real device. There must be some setting i am missing to allow inspection of webview.
I thought maybe I need to build for debug. But when I tried that, it didn't make any difference for inspection (both debug and non-debug work on GenyMotion, but not on real device). But if I build for debug everything in the UI is really tiny!
I can probably get by for now on GenyMotion. Bu there are some appearance differences on real devices, and it would be handy to have this working.
|
|
|
|
Post by Vladimir Musulainen on May 23, 2017 7:18:36 GMT
Hi Jon,
I constantly use Chrome remote device webview inspector with rhodes applications and it works perfectly.
But some time ago I faced too with the inspector cannot connect with the webvie. I have an opinion that this may be connected to the device
|
|
|
|
Post by Alex Epifanov on May 23, 2017 8:48:39 GMT
Web inspector should work generally with debug builds, but it depends on device - I've had issues with some old Alcatel.
Never faced problems with popular Samsung models.
|
|
|
|
Post by jontara on May 23, 2017 15:45:48 GMT
Thanks, I tried a number of things, and haven't found a solution yet.
- try connecting USB directly to Mac, not to a USB hub
- try accept or deny MTP when connect with USB
Neither of these make a difference, and anyway, I DO see Chrome sessions in Chrome DevTools. Just not webview in Rhodes app. And yet I do see webview in Rhodes app on GenyMotion.
Debug/production build doesn't seem to make a difference. In fact, I seldom/never use debug build for Android, and was able to inspect on device in the past. And I can inspect on GenyMotion with production build.
Of course, it is up to my build.yml configuration to remove "debug" capability for real production builds. For now, I build with it always on.
(And I just caught something with another project I will email Konstantin about...)
|
|
|
|
Post by Alex Epifanov on May 23, 2017 22:51:13 GMT
Jon if you share your app sources and apk I'll take a look.
|
|
|
|
Post by jontara on Jun 25, 2017 19:33:42 GMT
Alex: it can be demonstrated with the Technician app that you have access to. I just tried, and was unable to see it in Chrome desktop remote devices on a Galaxy S7 running Android 7.0.
I AM able to see Chrome browser, though, running on same device.
I AM able to see the app webview when running on GenyMotion.
I can give you access to the other app I am working on, but I think there is no difference, as neither one is able.
I have in the past been able to remote-inspect Technician app on device with desktop Chrome.
I built with a pre-6.0 Rhodes, hash 2fff85e0 but I don't think that's the issue.
|
|
|
|
Post by jontara on Jan 5, 2018 20:55:13 GMT
It won't work on real device unless you set build: 'debug' in build.yml.
AndroidManifest.erb has:
android:debuggable='<%= @debuggable %>'>
@debuggable will only be true if build: 'debug'.
But even rewriting AndroidManifest to just hard-code it to 'true' (and set capabilities: [debug]) it will not work. There must be something else that is changed as well by build: 'debug'.
It doesn't seem to matter if you build using device:android:debug or device:android:production. You have to set build: 'debug'.
For simulator (at least GenyMotion) none of this matters. It just works!
|
|
