Chrome 77 remote device debug issue - google-chrome

Is any one facing issues with remote device debug on Chrome 77 on Mac. I am unable to debug android device on Chrome 77.

A weird but functional solution without having to download an old version of chrome: https://support.google.com/chrome/thread/15368759?msgid=15847043
Download / Open Firefox
Navigate to about:debugging#/setup in Firefox
Disable USB Devices and Enable it again in Firefox
Go to Chrome chrome://inspect/#devices. You will now find your device(s) listed

I too faced the same issue regarding chrome version 77 in windows too.. Kindly download the previous version like 73 or 74..
https://www.neowin.net/news/google-chrome-730368386-offline-installer/

Related

TWA Issue ~“Please install Chrome Stable 72 or later” for Android 11 Version

For Android Version, less than 11 My app is working fine. But for the versions of Android 11, it shows a message " Please install Chrome Stable 72 or later" when I try to open the app.
Change dependency from
implementation 'com.github.GoogleChrome:custom-tabs-client:a0f7418972'
to
implementation 'com.google.androidbrowserhelper:androidbrowserhelper:2.2.0'
Also make sure Launcher activity in manifest imported from androidbrowserhelper
com.google.androidbrowserhelper.trusted.LauncherActivity
More migration details you can found here
Trusted Web Activity was introduced in Chrome version 72. The issue there is not related to the Android version, but that the version of Chrome installed on the devices showing this message is earlier than 72.
installing the latest version of Chrome from Google Play should solve the issue.

--Headless mode is not working in chrome version 77

Previously I am working on chrome 76 version then my headless option in selenium testing is running fine when the chrome is updated with version 77, this is not working I use this for writing basic automation tests in selenium even if I mention chrome options to --headless that doesn't work for me. It directly opens the browser but if we use --headless the browser need not to open but in my case, it was opening. Please suggest me a way to get this issue resolved
Yes, right now the chrome is updated again and for the latest update to 78 version, this --headless mode is working fine. Now if I use 77 chrome driver its working for me.

In-line extension installations no longer work in Chrome 56

After upgrading to Chrome 56 on Mac, it seems that inline Chrome extensions no longer prompt an installation anywhere on the web.
Does anyone know why?
Console gives the following error message:
Uncaught Error: A Chrome Web Store installation is already pending.
at Installer.install (extensions::webstore:20)
at Object.install (extensions::webstore:82)
at installChromeExtensionm ((index):643)
at HTMLAnchorElement.onclick (VM1380 :1)
This seems to be an issue for all websites that have inline Chrome extensions (try grammarly.com, or momentumdash.com) - tested with multiple macbooks using Chrome 56.0.2924.87

How do you install flash debug version with Windows 10

I have been looking for a way to install the debug version of flashplayer for ie11 or the newer microsoft edge browser under Windows 10. AS far as I understand, the flash plugin is now embedded with both browsers, so there is no way to update it to a debug version.
Using the debug version installer from adobe site (active x version), gives me a pop-up stating that I already have the latest verion which is true, but there seems to be no way to change my version with the debug one.
AS anyone succeed in using the debug version of flash undex one of these browser on Windows 10 (64bits)?
Thanks,
Currently the answer is no, you can not use the Flash debugger in Windows 10 / IE or Edge browsers as they are 'embedded' libraries in the OS now. The options are to use Win 10 & Firefox or use Win 8.1 when debugging Flash.
Via: https://forums.adobe.com/message/7841726#7841726
I have received confirmation that at this time Microsoft does not
support the debuggers on Windows 10. We do not have an estimate as to
when they will support the debuggers, but when they do, the install
links will be added to the Adobe Flash Player Support Center page.
You might do it manually by yourself, the core step is running flash_debugger installation file with switch -install, after a few modification in debugger folder, then you might reach there.
showing the happy result in image following.enter image description here
Download the windows 7 virtual machine for free. I recommend Virtual Box. https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/
Once you have Windows 7 running inside Windows 10, install the IE Flash debugger or another of your choice. https://www.adobe.com/support/flashplayer/debug_downloads.html
IE 11 does not support flash player content debugging in windows 10.Fire fox and Chrome browsers however allow for the content debugging in windows 10.
1)Install Flash debugger for Firefox or Chrome:
a) Go to https://www.adobe.com/support/flashplayer/debug_downloads.html
b) For fire fox, Download and install Download the Flash Player content debugger for Firefox - NPAPI
c) For Chrome, Download and install Download the Flash Player content debugger for Opera and Chromium based applications – PPAPI

WebGL doesn't work under Chrome in Windows 8 Developer Preview

Hi I was wondering if anyone else was having problems running WebGL in Windows 8 under Chrome.
I'm using Windows 8 Developer Preview x64 and Chrome 18. My video card is a Nvidia 250 GTS.
If I try to run any WebGL page, running though javaScript or NativeClient both fail to load thinking my video card doesn't support it.
I have my own native OpenGL apps that use GL2 and GL3 API features... GL itself is not the issue, unless I don't understand how Chrome uses GLES2 features.
Are there any known bugs about this?? Can't find anything.
EDIT: I just installed 'Windows 8 Consumer Preview x64' and WebGL still does not work... Is there a black list of OS's, kinda like some Intel video cards are black listed?? I have my system dual booted with Arch Linux and WebGL works fine on there?
As a workaround on windows 8 just add --disable-gpu-sandbox (I've checked it on 18 and 19 versions). To check open chrome://gpu/
For more information see chromium issue