I once came across an SO answer that gave a Chrome URL to navigate to, that had a button to "enable" JS console logging. After enabling the logging, that tab would show the console logs of other Chrome tabs.
I know this answer seems like a duplicate, but I'm having a lot of trouble finding how to do that again. It was super convenient since it gave the console logs on any Chrome browser without needing a USB connected.
Any ideas? I know I came across it in an SO question about iOS debugging.
Found it! So, it's actually a Chrome on iOS only feature.
URL: chrome://inspect
That URL won't show anything on Chrome for Android, which tripped me up. But, on iOS it shows a "Start Logging" button.
Answer from: https://stackoverflow.com/a/55433616/2096769
When I start Postman I see the icon appear in the Dock and in the Force Quit window, and I can click on the icon in the dock and Postman appears in the menu bar, with the single option "Quit Postman." So it's running, but the window doesn't appear. This morning I upgraded Chrome to 55.0.2883.95, Chromium to 58.0.2991.0, and Chrome Canary is at 58.0.2990.0.
Is there a way to switch Postman from Chrome to Chromium or Chrome Canary (i.e., to test Postman with different builds)? Or to revert Chrome to any older build? Or any other ideas to get Postman working?
The chrome addon for Postman will be depricated soon.
There are now fully functional standalone apps for Windows/Mac/Linux here. They work just as well as the Chrome addon and even have some additional features. I would suggest moving to the standalone apps.
In Chrome I googled "Postman," which took me to the Chrome App store, and the Postman page has a green button for "Launch App Now." That worked!
try disable and then enable the extension.
It worked for me.
Sometimes google chrome doesn't load it properly.
I had a nearly similar problem, where Chrome postman app (extension) fails to post/get/etc. It was unable to access the internet for some reason. After trying many solutions, it seems that the javascript setting in Chrome was causing it. You need to enable javascript in Chrome, restart Chrome, then the postman app will work.
I am trying to debug my android web application which I had written by Ionic framework and AngularJS and is rendered on webview browser on android platform by chrome://inspect#devices but I am seeing this screen:
here is the picture
it was working perfectly for last 5 months but now it is killing me.
I tried uninstalling chrome, reset settings, reset dev.tools but they were not practical solutions.
In addition, it is working fine while inspecting a regular website on google chrome
You should try to test it with a fresh ionic app, and you will see if it's problem of your app or chrome.
In case that it's chrome problem, try to open an emulator and inspect it, maybe it's Android problem or USB error.
Hi I was using selenium chrome drivers as interactive service to open some websites. It was working fine. Suddenly found that the session is not loading correctly and showing black page. Found following error:
chrome automation extension has crashed. click this balloon to reload the extension
Found that with chrome browser version was updated to v51 and selenium-chromedriver 2.21 is compatible with v50.
Downgraded chrome browser to v50. Now it is working fine.
So i have been running into this problem with a lot of Wordpress sites lately, usually occurring when i am logged in as Admin, so i couldn't post here because no one would be able to view the problem. However, i just found a site that it happens on that doesn't require admin creds.
http://www.otisports.com/
When i visit this site in Chrome (Version 34.0.1847.137 m), it just displays a blank page. No errors, just the (what now seems standard) event.returnValue is deprecated. Please use the standard event.preventDefault() instead. warning. I have seen that warning signify problems on the site, but they are usually minor, not to the extent that the above URL displays. However, if i open an Incognito window and visit the site everything works perfectly and there is no warning. Does the Incognito window deal with webpages in a way that is so entirely different that it would cause something like this to happen?
I have been racking my brain trying to figure this out. Can anyone reproduce this? is it a bug in chrome?
EDIT: I just tried to open a bounty on this question and the EXACT same thing happened. In Regular Chrome, nothing happened when i clicked the start a bounty link and i saw various errors Undefined is not a function however in incognito everything worked perfectly. what gives?!
EDIT: Yes, i have cleared the cache, history, cookies, everything, and i still get the same errors. I cant even post a comment on this question because of errors...
I came across the same issue when trying to open evernote.com. It loaded successfully while using incognito mode in chrome. Let me share how I fixed this even though the original post is way too old. But maybe someone can find it useful.
I'm using chrome (Version 73.0.3683.103 (Official Build) (64-bit)) running on Linux Ubuntu 18.04.2 LTS.
I tried disabling all extensions and clearing browser data/cache but nothing worked. PS: Disabling adblock previously worked for me. Yes, I stumbled over the same issue before and whitelisting evernote in adblock solved the issue. But it didn't now.
The following is what worked for me:
Open developers tools (CTRL + SHIFT + J).
Navigate to Applications tab.
Choose Clear storage from the side menu
Hit Clear site data button.
After reading the comments I dug into chrome and saw there was a bunch of extensions still sitting around that were definitely malware and I thought I had previously deleted. Instead of picking through them one-by-one, I just deleted everything, re-installed Chrome, and now everything works great!
I had the same issue. My application was working in Incognito mode and in Firefox but not in Regular Chrome. I even disabled all the extensions but no luck. I eventually cleared the Cached images and files because on developer console I found out that the regular chrome was still picking up the old file due to caching. So as soon as I cleared it, my app showed up like a rocket :)
Try removing any non required extension .
Specifically AdBlock
I resolved the problem post that.
Since on Incognito , extensions are disabled, hence page run as expected.
I resolved this unforeseen issue using following steps.
CTRL + SHIFT + DEL > Clear Browsing Data.
Cookies and other site data
Cached images and files
This is for Chrome Browser.
Open Console (Ctl+Shift+I) first.
Then under the application tab, you will find some options on the left, find out the application there, you will find it at the top.
There you will find Service Workers.
Under Service Workers, there will be three checkboxes. Select Update on reload checkbox and reload again.
I had the same issue after installing React-Sight Extention.
The Page hanged but not in the incognito mode.
Try deleting any recently added or junk extension.
Delete your cache.
That worked for me
I had a similar issue in chrome, in my case the problem was that I could log in to my university library's website only in incognito mode. After some digging, I figured out that Google Translate extension was set to automatically translate any page. When I turned that off and instead selected never translate that specific page, it started working in the usual mode as well.
This is rather an old issue but still happens. None of the solutions recommended here and there did not solve the issue in my case.
I somehow noticed this is related with a -some kind of- corruption on the user profile.
This is how I solved it:
Close all Chrome browsers.
Open a Google page on Chrome.
Sign-out from Google (rigt click your profile picture on a Google page, not on the Chrome itself), and sign-in.
If this doesn't work:
Close all Chrome browsers.
Right click Chrome icon and select Google Chrome.
Delete your Google profile on the "select your profile" page.
Close Chrome.
Open Chrome, sign-in.
uBlock Origin was the culprit in my case. Once I allowed the site in uBlock Origin, pages loaded correctly in normal Chrome.