Remote debug broken with Android Chrome 89 - google-chrome-devtools

When I want to inspect a page listed on chrome://inspect page on a remote Pixel 4 with OS version 11, I get a white page with just 'HTTP/1.1 404 Not Found' shown.
I uninstalled all updates from Android Chrome, went down to version 83, and remote debugging started working again.
I have the same problem with current versions of Chrome beta/dev/canary.
Is this only a problem on my device, or a general problem? Any way to get remote debugging working with Chrome 89?
Thanks,
Michael

It seems you can't get it working on Chrome 89 for now because this is a general problem. I got the same issue on Vivaldi 3.7 which runs Chromium 89. The only option for now is rolling back to previous working release.

Related

Can't navigate to url in Google Chrome Android Emulator, just says Data;,

I am using eclipse, Appium 1.6.4 and Android Studion with Android 7.0 also tried with 6.0.
I run my automated test and it executes, it connects to the device, it opens the chrome browser but then doesnt navigate to the google url using the driver.get(...) method it just says data;, . I dont get any errors until it eventually times out and tries running it again.
Any help would be appreciated as ive tried a few things and got nothing.
Thank you.

protractor not connecting to chrome

I am using protractor#3.2.2. It was working fine with chrome all these days. But all of a sudden it is not able to connect to chrome(chromeDriver).
It says
SessionNotCreatedError: session not created exception
It is able to connect to Firefox and Edge.
I am using chromeDriver#2.21
Any ideas about how to fix it?
The chromeDriver 2.21 supports till chrome version 53, But i was using chrome version 54. This is the reason why the chromeDriver is not able to connect to chrome.
Once i downgrade to chrome version 53, everything started to work as expected.
So if you guys face the same issue, check your chromeDriver version and your chrome version.

Chrome for window devtools freezes

I'm using chrome on Windows 7 and after updating from 48 to 49, the devtools get frozen when I'm trying to navigate some of the tabs (sources, resources, etc.)
I re-installed several times, and restored devtools options to default, but none of the attempts worked for me.
I downgraded to 43 and works fine.
Anyone knows the reason or experiencing same problem?

Breakpoints in Chrome Dev Tools can't be hit while the url has a hash

http://fiddle.jshell.net/dZBY2/1/show/light/#1
As I did a demo page above, after marking a breakpoint,I fresh the page ,the breakpoint can't be hit.
Am I did something wrong ? It was amazing.
My Chrome version :31.0.1650.63 m.
My OS: Windows7 64bit
This issue https://code.google.com/p/chromium/issues/detail?id=306239 was fixed recently. The fix is available in Chrome Canary or Beta and will reach stable channel in a few weeks.

Windows Phone SDK 7.1 Emulator Complete Re-boot Error

I thank you all for reading this lengthy question. It's really important and I will appreciate it if you can assist me :)
The problem -------
I am have been using the Windows 7.1 SDK for about two months now. The emulator has worked without any problem so far. However, today, it began displaying this error (The saved state (Name of File).dess is corrupt. Please delete the corrupted saved state file and then retry). I had not made any significant changes to my project code, or moved any files. I had just added some Visual State animations for a button.
As it suggested, I went ahead to delete the file. I then started debugging again. However, the emulator now opened and displayed the message (Windows Phone Emulator is doing a complete OS reboot). This message was displayed for a very long time. I closed the emulator and project. Since then, I have been unable to use the emulator. I am able to code normally in Visual Studio, but I cannot test my application.
What I have tried ------
I read up on this issue and found many others who faced the same emulator issue. Following their suggestions, I have run one repair of the Windows Phone SDK 7.1. I have also tried uninstalling and then re-installing the SDK 7.1 once.
System Specifications -----
I am using Visual Studio Express 2010 for Windows Phone (Windows 7 64 bit)
I have downloaded the Windows Phone SDK 7.1 from this link: http://go.microsoft.com/fwlink/?LinkId=258412
I have read that this issue might be because of some hardware incompatibility. However, I think my machine is compatible with the emulator. Here is some information.
DirectX Version: DirectX 11
8GB RAM
Driver Model: WDM 1.1
Additional Information:
I have read that installing the 'January Update' might fix this issue. I tried downloading the update from this link: http://www.microsoft.com/enus/download/details.aspx?id=23854
However, the installer said that the update is not compatible with the product/version of the product I am using.
Usually the Repair function of the WP7.1 SDK is enough to fix all the issues. It runs the generation of the saved state of the emulator again.
Please try to delete files in %ProgramData%\Microsoft\XDE folder first (make sure you backup them somewhere else.), then run the emulator. If the emulator runs with a message "Windows Phone Emulator is doing a complete OS boot," let it boot. It takes some time though. This way you will know that the emulator actually can run on your computer. This won't generate a new saved state image, but the emulator should at least load.
Next, try installing WP7.1.1 SDK update from http://www.microsoft.com/en-us/download/details.aspx?id=29233. This update also installs additional 256MB emulator image besides the original 512MB image. It also generates emulator's saved states in the process, potentially fixing the issue.
If everything fails, then try these instructions to fix the saved state of the emulator:
Uninstall WP7.1 SDK
Manually delete these folders:
%ProgramData%\Microsoft\XDE
%LocalAppData%\Microsoft\XDE
Install WP7.1 SDK again.
Install WP7.1.1 SDK update: http://www.microsoft.com/en-us/download/details.aspx?id=29233.
Edit:
Btw, have you tried to reboot your computer? Once this fixed the issue for me.
Alright, I managed to solve this problem.
I reinstalled Windows and downloaded the SDK 7.1 again. The emulator works fine now!
#Paulos, thanks for helping!
I had the same problem for a long time. Try this:
Start up Visual Studio 2010, but before you start debugging, click on the tabs of all the open pages so that all the xaml pages and code behind pages can load.
I noticed it when I opened Visual Studio, but the first open page was a code behind page and not an xaml page, so when I first clicked on the tab of a xaml page, of course, it took some time to load the xaml page into the editor. However, when that and one or more open xaml pages were also loaded, the emulator started without the error message.