Unable to open the Chrome DevTools in Gmail and Google Drive

[sha]

Hi all,

This is a recent issue that I ran into yesterday (6/18/19) when attempt to open the dev tools in Chrome (Version 75.0.3770.100 (Official Build) (64-bit)) in gmail on MacOS (Version 10.14.5). When I attempt to open the inspector with the shortcut (opt + command + i) nothing happens, when I click on View > Developer > Developer Tools (or Inspect Elements/Javascript Console) in the top navigation nothing happens, when I right-click the option 'inspect' is disabled and I cannot select it. To be clear, both these options work for other sites for me it's specifically an issue on Gmail and Google Drive (docs, etc). If I have the dev tools open in a given tab and then navigate to Gmail it closes (doesn't matter if the window is docked or not). This issue doesn't seem wide spread but there are a couple others at my job that have the same issue. 

Some steps I've taken to resolve this issue:

* Checked that `DeveloperToolsDisabled` isn't set to true here: chrome://policy/ 

* Clearing all my cookies/cache/storage/etc and restart Chrome

* Uninstall and reinstall Chrome

* Use incognito where extensions aren't enabled

None of these helped. It's actually pretty impactful for me as I work on a team that supports emails and I need to be able to make updates for our newsletters for specific clients. While I can debug in other browsers like Firefox, going to another browser really isn't an option sometimes.

[PhistucK]

When you open the Chrome task manager (on Windows, this is Shift + Escape), does GMail and Google Drive show up as "App" by any chance?

If so, it might be related, I think they are default Chrome applications.

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Chrome DevTools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/8a7fae03-c0b9-4e7e-830b-802a1051e5ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sha]

Yes, for tabs that are open it's `Tab: [title of page]` but for gmail it's `App: [title]`. Is this a new feature? Is there a way to change the settings from 'App' to 'Tab'?

[PhistucK]

I would guess it is a bug. Maybe someone from the team will chime in.

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Chrome DevTools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/dd5cd7bf-e9b5-4332-97bc-10e9da7609dc%40googlegroups.com.

[sha]

Update: This is still an issue for Chrome but I am able to open the dev tools for gmail on Chrome Canary.

[Erik van den Hoorn]

I am experiencing the same behaviour with Google Chrome 81.0.4044.113. However, I have multiple G Suite accounts and this issue only occurs with some of them. Signing in using an incognito window with the affected G Suite account does not solve this issue.

[Erik van den Hoorn]

Started looking into settings specific to the G Suite environment and discovered there are some force installed extensions. When I looked under chrome://policy/ I found that DeveloperToolsAvailability is set to 0. This are the different settings:

0 = Disallow usage of the Developer Tools on extensions installed by enterprise policy, allow usage of the Developer Tools in other contexts

1 = Allow usage of the Developer Tools

2 = Disallow usage of the Developer Tools

I assumed that on of the force installed extensions is activated in Gmail and Google Drive and then the developer console is blocked by this setting. So I signed in to admin console and changed the setting to 1 in the Chrome Management settings. Now I am able to open the developer console again. 

[Yang Guo]

Hi Erik,

thanks for these updates! Glad that you were able to figure this out!

Cheers,

Yang

--

You received this message because you are subscribed to the Google Groups "Chrome DevTools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/bd013e18-d1b7-4786-b466-cc12d09852e6%40googlegroups.com.

[Erik van den Hoorn]

Hi Yang,

No problem. I hope it can still help sha or anyone else reading this thread.

Cheers,

Erik

On Tuesday, 21 April 2020 14:50:43 UTC+2, Yang Guo wrote:

Hi Erik,

thanks for these updates! Glad that you were able to figure this out!

Cheers,

Yang

On Tue, Apr 21, 2020 at 2:09 PM 'Erik van den Hoorn' via Chrome DevTools <google-chrome-developer-to...@googlegroups.com> wrote:

Started looking into settings specific to the G Suite environment and discovered there are some force installed extensions. When I looked under chrome://policy/ I found that DeveloperToolsAvailability is set to 0. This are the different settings:

0 = Disallow usage of the Developer Tools on extensions installed by enterprise policy, allow usage of the Developer Tools in other contexts

1 = Allow usage of the Developer Tools

2 = Disallow usage of the Developer Tools

I assumed that on of the force installed extensions is activated in Gmail and Google Drive and then the developer console is blocked by this setting. So I signed in to admin console and changed the setting to 1 in the Chrome Management settings. Now I am able to open the developer console again. 

On Tuesday, 21 April 2020 12:21:44 UTC+2, Erik van den Hoorn wrote:

I am experiencing the same behaviour with Google Chrome 81.0.4044.113. However, I have multiple G Suite accounts and this issue only occurs with some of them. Signing in using an incognito window with the affected G Suite account does not solve this issue.

On Tuesday, 24 September 2019 17:17:11 UTC+2, sha wrote:

Update: This is still an issue for Chrome but I am able to open the dev tools for gmail on Chrome Canary.

On Wednesday, June 19, 2019 at 4:21:50 PM UTC-4, sha wrote:

Hi all,

This is a recent issue that I ran into yesterday (6/18/19) when attempt to open the dev tools in Chrome (Version 75.0.3770.100 (Official Build) (64-bit)) in gmail on MacOS (Version 10.14.5). When I attempt to open the inspector with the shortcut (opt + command + i) nothing happens, when I click on View > Developer > Developer Tools (or Inspect Elements/Javascript Console) in the top navigation nothing happens, when I right-click the option 'inspect' is disabled and I cannot select it. To be clear, both these options work for other sites for me it's specifically an issue on Gmail and Google Drive (docs, etc). If I have the dev tools open in a given tab and then navigate to Gmail it closes (doesn't matter if the window is docked or not). This issue doesn't seem wide spread but there are a couple others at my job that have the same issue. 

Some steps I've taken to resolve this issue:

* Checked that `DeveloperToolsDisabled` isn't set to true here: chrome://policy/ 

* Clearing all my cookies/cache/storage/etc and restart Chrome

* Uninstall and reinstall Chrome

* Use incognito where extensions aren't enabled

None of these helped. It's actually pretty impactful for me as I work on a team that supports emails and I need to be able to make updates for our newsletters for specific clients. While I can debug in other browsers like Firefox, going to another browser really isn't an option sometimes.

--
You received this message because you are subscribed to the Google Groups "Chrome DevTools" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.

[sha]

Thanks for sharing this info Erik! I'm not sure when but this issue resolved itself but I will keep this in my back pocket in case this comes up again. I'm using an enterprise G suite so that could have definitely a part.