Console messages don't display, even though X-ChromeLogger-Data header exists

Question

Console messages don't display, even though X-ChromeLogger-Data header exists

Opened this issue 9 years ago · 9 comments

I'm trying to use chromelogger in an SPA. I make ajax calls, and on the server side I use chromelogger on that request. When the request completes I can see a lot of data in the X-ChromeLogger-Data header, but I don't get data in my console. occasionally the data shows up, but most of the time it doesn't.

Any ideas? The chromelogger icon in chrome is enabled. I'm on chrome 42.0.2311.13. Just installed the chromelogger extension yesterday so I'm on the latest version.

Thanks.

Answer 1 · 2015-05-07T14:11:54.000Z

Have you clicked the icon to make sure it is toggled on?

Answer 2 · 2015-05-07T14:12:46.000Z

Yes as I said the chromelogger icon is enabled. I've togged it off and back on to see if that made a difference and it didn't.

Answer 3 · 2015-05-07T14:25:48.000Z

Ah sorry about that... hmmm... Can you try it on a regular request that is not ajax?

If you go to https://craig.is/writing/chrome-logger and open the console and toggle on the extension do you see the logs?

Answer 4 · 2015-05-07T14:27:26.000Z

Interesting... I am actually not seeing them show up every time too. I wonder if this is something specific to a new version of chrome. I will have to dig into it more later.

Answer 5 · 2015-05-07T14:31:58.000Z

Thanks. I noticed the irregularity when testing on a single page also.

Answer 6 · 2015-09-07T10:15:49.000Z

Hi, I believe there's some race condition there. maybe _listenForLogMessages runs too late, after response is back?

Answer 7 · 2016-02-04T23:18:51.000Z

Doesn't work reliably I'm afraid. Probably because Chrome does goofy stuff to the headers/caches them? Its though to use in production.

Answer 8 · 2017-04-03T05:06:32.000Z

Is there a page where this is consistently reproducible or some other way I can test it?

Answer 9 · 2017-08-28T01:19:12.000Z

Well - just figured out the issue. In case anyone else has this issue - my issue was as simple as not selecting the Info type errors in the console. For anyone else experiencing this issue in getting messages in Chrome developer console make sure the error types you want to see are selected.