Unable to inspect or debug logs on extension on chromeOS force install by enterprise aacount

[Yagna Pathak]

I am currently utilizing ChromeOS, where I've developed an extension that has been forcibly installed through enterprise policies. While I can observe the extension upon logging in through my enterprise account, I am encountering difficulties when attempting to debug and review console logs using the inspect elements feature on browser.

Guide me on this. 

[Patrick Kettner]

Hi Yagna,

devtools are not available by default on forcibly installed extensions. You can override this if you are also able to set the DeveloperToolsAvailability to "1" (which equates to "Allow usage of the Developer Tool").

If you don't have the ability to modify the policy, then I am not aware of a way to circumvent that on the device.

On Fri, Oct 27, 2023 at 5:41 AM Yagna Pathak <ya...@solvative.com> wrote:

I am currently utilizing ChromeOS, where I've developed an extension that has been forcibly installed through enterprise policies. While I can observe the extension upon logging in through my enterprise account, I am encountering difficulties when attempting to debug and review console logs using the inspect elements feature on browser.

Guide me on this. 

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/852294e7-a9af-4d67-8c9a-9b77f12cc2bbn%40chromium.org.