Chrome: console.log, console.debug are not working

Question

Console.log and debug not printing, only return undefined. Why it can be? I've tried to re-install chrome, but it doesn't help.

Here is screenshot from chrome's main page, so functions are not redefined in some code console.log doesn't work

For anyone doing web development with Flask: I ran into this same issue -- adding console.log statements to my Javascript, and nothing was displaying in the console. Problem turned out to be due to browser caching... it wasn't seeing my added log statements. Solution is a hard refresh (CTRL+F5 instead of F5 on Windows). Hope that helps someone else with the same issue! — Joel Wigton, Oct 03 '19 at 17:55
2021 and still the same problem. So every time I want to console.log something I need to press Ctrl+F5. — yendrrek, Jan 27 '21 at 16:03
**Sometimes the website overrides the default (window.) console.log** :) — jave.web, Jun 09 '21 at 13:15

score 369 · Accepted Answer · edited Apr 04 '18 at 06:07

369

Click “Default levels” and make sure that "Info" is checked. By default it is only set to show Errors and Warnings

I came here with the same problem :/

edited Apr 04 '18 at 06:07

Kalanos

3,922
3
37
63

answered Sep 17 '13 at 15:26

Alexey Borovikov

3,814
1
12
7

3

Thanks...I just thought the new version chrome does not work well ! – Keating Nov 01 '13 at 04:56
18

@NikhilPatil not stupid at all. That's just a terrible default setting. – corbin Nov 22 '13 at 14:36
Me too feeling stupid.I even reported an issue, that chrome developer tool is not working. – sudhAnsu63 Nov 26 '13 at 07:38
also with newer versions: if javascript is disabled, console just goes blank after enter. won't tell you what the problem is. enabling javascript on that site does enable the console again. – hakre Aug 23 '14 at 09:42
Strange, cause i have encounter a situation where inside a script tag it's not working.. and inside a js file it works.. very strange xD – Andrea Bori May 27 '16 at 12:02
With all those settings correct, I updated Chrome from v52 to v53 in mac and it started working . version problem for me ! – peevesy Sep 06 '16 at 10:17
6

Just a note for later versions of Chrome: it looks like it's a dropdown at the top now, and you'll want to change it to "Verbose" to see everything. – GreatBlakes May 05 '17 at 19:48
how is this a thing?! – Kalanos Apr 04 '18 at 00:26
Nice. I agree with @HashRocketSyntax - How is this a thing? This will be very helpful in the future... – user2796515 Mar 08 '19 at 15:37
"Default levels" greyed out, cannot click, i.e. cannot change ... Figured it out: There's a message tree in the left sidebar, one of the items is "info"! – Ralf Mar 05 '20 at 15:57
and where is deafult levels – Cybernetic May 25 '20 at 13:23
5

This solved my slightly different error: I had accidentally typed something into the "Filter" box (next to the levels dropdown) the day before. – JoshuaCWebDeveloper Aug 22 '20 at 16:56
i have checked all levels still not working ? – Ali Yar Khan Nov 03 '21 at 07:23

score 55 · Answer 2 · answered Jun 22 '14 at 09:24

55

For completeness: In the current version of chrome, the setting is no longer at the bottom but can be found when clicking the "Filter" icon at the top of the console tab (second icon from the left)

answered Jun 22 '14 at 09:24

Friedrich Große

2,195
17
19

RBT · Answer 3 · 2022-03-24T12:13:37.677

As of today, the UI of developer tools in Google chrome has changed where we select the log level of log statements being shown in the console. There is a logging level drop-down beside Filter input box. Supported values are Verbose, Info, Warnings and Errors. The default selection in the drop-down is Info.

Any log whose severity is equal or higher will get shown in the Console tab e.g. if selected log level is Info then all the logs having level Info, Warning and Error will get displayed in console.

When I changed it to Verbose then console.debug and console.log statements started showing up in the console. Till the time Info level was selected, they were not getting shown.

score 25 · Answer 4 · answered Feb 21 '18 at 20:18

25

Same issue, but I just cleared my settings. I went into Settings > Preferences and Clicked [Restore defaults and reload]. Just remember what your settings were.

answered Feb 21 '18 at 20:18

Tim

369
3
4

I spent days on debugging this issue, and this solution worked like magic! – Aliya Oct 08 '18 at 05:06
I used this but I ticked disable cache under Network and that then worked – dave Oct 23 '18 at 09:17
I spent 3-4 hours trying to work out why Next.js wasn't running any code on the client side while working on a technical assignment for a new job, turns out this was all that was wrong. I have no idea why it was broken but the SO post may have saved my chances of getting an amazing job – DanielM May 10 '20 at 11:48
2

If you can't find these settings, press F1 inside the dev tools. – gust Jan 07 '21 at 15:12

score 23 · Answer 5 · answered Jan 08 '20 at 14:22

23

Make sure that the "Filter" input is left blank and nothing is written intentionally or by mistake. That was it in my case :P

answered Jan 08 '20 at 14:22

Deval Khandelwal

3,337
1
25
37

4

It remembers this across sessions -tripped me up as well. – Le-roy Staines Mar 11 '20 at 06:15
2

THIS IS IT! Thank you – Arman Karimi May 19 '21 at 09:17

score 13 · Answer 6 · answered Nov 09 '15 at 12:14

13

I experienced the same problem. The solution for me was to disable Firebug because Firebug was intercepting the logs in the background resulting in no logs being shown in the Chrome console.

answered Nov 09 '15 at 12:14

Memet Olsen

4,508
5
37
49

score 12 · Answer 7 · answered Jul 09 '18 at 18:04

12

There could also be some filters applied to the console. Remove them.

answered Jul 09 '18 at 18:04

Adriana

141
1
3

Reg Edit · Answer 8 · 2020-07-08T13:56:47.767

As of July 2020 the Chrome UI has changed once again and the logging level dropdown doesn't seem to do anything now.

Instead, there's a new pane to the left of the main console pane, which may have got unintentionally set to one of the restrictive logging levels:

Select the top category (messages) to reveal all the logging:

EDIT: EVEN THEN Chrome seems to add things to the Filter box, which again loses some logging, so you must CLEAR THE FILTER BOX TOO!

(Filter box is at the top of both my pics above, under "Network conditions"; you can see that it has some contents about "urlwebpack" which I didn't put there!)

_THE_ new answer. It shouldn't be this hard ಠಿ_ಠ – ps2goat Jul 07 '21 at 12:36 — ps2goat, Jul 07 '21 at 12:36

score 5 · Answer 9 · answered Jun 02 '17 at 06:46

5

In my case was webpack having the UglifyPlugin running with drop_console: true set

answered Jun 02 '17 at 06:46

ianaz

2,403
2
27
36

1

I have the same problem. uglify is removing the logging. Thank you – Krishna Vedula Feb 14 '18 at 12:08
Is it possible to restore it once a site script drops it like that? – PSkocik Jan 02 '19 at 10:54

score 4 · Answer 10 · edited May 31 '18 at 09:17

4

If you are seeing(3 messages are hidden by filters. Show all messages.) then click on show all message link in Chrome dev tool console.

Because if this option enabled by mistake the console.log("") message will show but this will in in hidden state.

edited May 31 '18 at 09:17

RBT

21,293
19
144
210

answered Jan 17 '14 at 10:45

Nandu Hulsure

123
1
7

score 4 · Answer 11 · answered Jan 16 '17 at 12:32

4

I'm working on a site where some JS (or other) code is preventing console.log from working (console.log is probably overwritten). You can test this by checking if console.log works on a different page (like this one).

I don't have time to investigate further right now so used alert("something is: "+something) to get the info I wanted from a snippet I needed to run.

answered Jan 16 '17 at 12:32

avjaarsveld

579
4
9

https://forum.xda-developers.com is an example of a prominent site that disables `console.log`. – Dan Dascalescu Feb 03 '19 at 23:36

score 3 · Answer 12 · answered Oct 02 '18 at 12:36

3

Selecting verbose fixed it for me

answered Oct 02 '18 at 12:36

Ty Harlacker

111
1
4

score 3 · Answer 13 · edited Nov 01 '18 at 07:37

3

Click “Default levels” right next to filter and do make sure that "Info" is checked.

Please see screenshot:

enter image description here

edited Nov 01 '18 at 07:37

Unheilig

15,944
193
67
96

answered Nov 01 '18 at 07:15

Amir shah

187
7

This just duplicates [the accepted answer](https://stackoverflow.com/a/18853868/3303195) with a screenshot. You could make a better contribution by suggesting an edit to the currently accepted answer to include your screenshot. – faintsignal Dec 05 '18 at 03:06

score 3 · Answer 14 · edited Sep 03 '20 at 16:19

Sometimes the simplest things trip us up...

Type console.log in the console and check what function gets returned. If you see ƒ log() { [native code] } then it's something else. If you see ƒ (){} then somewhere down the line the native console.log function was changed.

Was working on a client's site today and that was the issue. If that's the case, you can either manually restore the console.log function or use console.dir() or console.warn() instead.

If you see ƒ (){} then there is a possibility that sometime console stops working due to some functionality you have added in your javascript. so first close all tabs restart chrome and in a new tab just typ1 console.log('hi'); if it prints that then it confirms that the problem is there in your script code. if not then restore the cosole.log.

To restore the console in new tab go to console and type delete window.console it will return true after that restart the chrome and you are good to go.

in my case it was 3rd-side ad script, it is blocking console, then trying to load ad, then restoring console, but ad was blocked by CORS, and no console.log restoration occured — djdance, Sep 01 '20 at 11:27

score 3 · Answer 15 · answered Apr 02 '20 at 19:35

3

In my case preserve logs do the trick. I did everything to show the logs, but it goes away. I checked it and it works,

answered Apr 02 '20 at 19:35

Noman_ibrahim

420
5
11

score 2 · Answer 16 · answered Mar 01 '18 at 09:15

2

In my case it was just an old cached Javascript file. After clearing the cache I saw my logs.

answered Mar 01 '18 at 09:15

Alex Osmolovsky

21
2

score 2 · Answer 17 · answered Dec 06 '19 at 10:02

2

In my case, i was not able to see logs because there is some text in Filter field, which caused results of console.log to disappear. Once we clear text in Filter field, it should show.

answered Dec 06 '19 at 10:02

Bharat

186
3
19

Thanks - fixed it for me! – Tony Jun 17 '20 at 12:55

score 2 · Answer 18 · answered May 09 '20 at 13:35

2

see if something show on the filter box in console ,it means something override your script clear the filter box and check again. i my case this is the issue.

answered May 09 '20 at 13:35

HeshanHH

533
5
9

score 2 · Answer 19 · answered Feb 16 '22 at 12:19

2

Another tip, why console.log doesn't works is that the Filter search field must be empty.

answered Feb 16 '22 at 12:19

Maxo

111
6

score 0 · Answer 20 · answered Aug 17 '17 at 10:08

0

This worked for me. In the console section, go to the settings on top right. There select preserve log and Log XMLHttpsRequests.

answered Aug 17 '17 at 10:08

Adarsh Trivedi

546
1
8
20

score 0 · Answer 21 · answered Apr 21 '20 at 10:30

0

Make sure the filter box is empty

answered Apr 21 '20 at 10:30

Ishan Rijal

1

score 0 · Answer 22 · answered Nov 02 '21 at 18:08

0

React Dev Tools Extension Causing the Issue

If you have React Developer Tools extension installed, unistalling it fixed my issue. Obviously this might be a difficult trade off.

I never used them so deleting them solved it in my case.

answered Nov 02 '21 at 18:08

dcts

951
9
26

score 0 · Answer 23 · answered Dec 20 '21 at 10:46

0

In my case, the solution was for me to click on "Top" and select debuggerWorker.aca... localhost:8081

answered Dec 20 '21 at 10:46

BigBros

41
7

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Dec 20 '21 at 11:24

Chrome: console.log, console.debug are not working

23 Answers23

React Dev Tools Extension Causing the Issue

Linked

Related