chrome://inspect/#devices opens a devtools window, but about the time it finishes drawing itself, it closes. No error messages
I'm trying to debug a website, not a native app. Any ideas why it would open and tease me, then close when the mouse gets near the window?
Linux: Version 40.0.2214.111 (64-bit) OS:14.04 Ubuntu
Android: Version 40.0.2214.109 OS: 4.1.2
More interesting details. It works on other tabs, and if I use one of those tabs that is working, and paste in my URL, it closes the devtools
As stated in the docs, your desktop Chrome must be newer than your Android Chrome:
Note: Remote debugging requires your version of desktop Chrome to be newer than the version of Chrome for Android on your device. For best results, use Chrome Canary (Mac/Windows) or the Chrome Dev channel release (Linux) on desktop.
For instance, you might install Chrome Canary/unstable or Chrome Beta on your computer. By using it instead, my inspector started working as expected. Currently, my Chrome Beta is v50 and the Android Chrome, v49.
Related
I would like to manually test my web app written in flutter which depends on an extension being installed in a browser.
Unfortunatelly when I try to debug it in android studio, it opens it in chrome, but the chrome does not allow me to install any extensions.
I couldnt find what executes the chrome, whether flutter or android studio, in any case i havent found way to edit chrome exec command in flutter or android studio.
So i installed flutter(i use zorinOS). After following some steps, i run flutter doctor and get:
[✗] Chrome - develop for the web (Cannot find Chrome executable at
google-chrome)
! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
I don't have any chrome in my os.I use brave as my default browser, and i have deleted my firefox(my previous browser). I just wonder, do i need to install Chrome specifically? Can't i just install Chromium or use other browser?
We don't test our development flow with Chromium, so I'm not sure.
This requirement is only necessary for development: debugging, etc. We rely on Chrome features to enable our development experience.
If I'm on a plane or do not have connectivity, remote debugging Chrome on Android fails with a blank window. What can I do?
When you remote debug, Chrome need a version of devtools that matches your mobile browser version. So it loads that specific version off the network. Once they are downloaded, they are kept in AppCache, so you only need to have network available once.
So as long as you start debugging a device (that particular Chrome version) once while you're online, you should then have all those files available later when you're offline.
But there's another workaround to avoid downloading the devtools version:
follow the instructions of https://developer.chrome.com/devtools/docs/remote-debugging-legacy down to (and including) the adb forward tcp:9222 ... section.
open http://localhost:9222/json/list (on your desktop)
find the tab you care about and copy the webSocketDebuggerUrl of it
wsurl = webSocketDebuggerUrl.replace('ws://','')
open this URL (on your desktop):
chrome-devtools://devtools/bundled/inspector.html?ws=${wsurl}
This will use your desktop's locally installed version of DevTools to inspect the phone. There is a possibility of a compatibility problem, but hopefully it should be small.
I'm trying to open Inspect WebView in chrome DevTools, i can see my device and the opened WebView, but when i click on the inspect link, the DevTools window opens for a brief moment and autoclose immediately.
Chrome version is 48.0.2564.116 (64-bit)
Issue was resolved by upgrading to Version 49.0.2623.110 (64-bit)
I have Samsung device with stock browser that called Internet.
The device is over 4.4 version.
I'm trying to remote debug the stock browser on a real device without success.
Already succeeded to remote debug chrome.
Is it possible on a real device and not on emulator?
The problem is just Samsung's stock browser
Hi!, Appium started to work with Android's stock browser (named.. Browser) since v1.3, the actual problem is the Samsung stock browser isn't Browser, it's Internet! These both apps are different (shame on Samsung!, not Appium guys fault). All other Android distributions that stock browser is Browser are working fine with Appium >= v1.3 as I've said before.
Emulator stock browser is Browser, that's why it's working for you on Emulator!
Why Appium doesn't work with Samsung's stock browser?
Appium are built to work with Chromium WebView (present on Chrome and Browser) , and Internet does not have it. So it doesn't work with Appium now, and probably won't work never, as Appium's maintainers does not have any interest to do the automation outside Chromium WebView. See this issue for more information: https://github.com/appium/appium/issues/4509
Ok, but how do I use Appium with Samsung devices?
So, the only solution is installing Chrome into your samsung device.
If you can't access the store to install the Chrome app, you can download and install manually the Chrome APK into your device (or other browser that uses Chromium webview, such as Chromium and ContentShell).
PS: ContentShell is basically only Chromium webview, without favorites, bookmarks and other common browser stuff, so it's pretty good for Appium testing.