See https://github.com/brave/brave-core/pull/4044
Developer tool doesn't load with remote devices in brave-browser (Desktop). Verified couple of brave versions, the issue persists on all the versions including latest released version.
0.67.125 - Dev tool doesn't load with remote devices
0.66.101 - Dev tool doesn't load with remote devices
0.65.121 - Dev tool doesn't load with remote devices
brave://inspect#devices in Desktopinspect under the device name in desktop
Developer tool window launches but never loads

Should load developer tool with remote devices
Always
All brave versions
@brave/legacy_qa
@GeetaSarvadnya this may be intentional
@pilgrim-brave would this be happening because remote debugging was disabled with https://github.com/brave/brave-browser/issues/1736 ?
Very likely.
Click on inspect fallback opens up devtool.

We want to re-enable this by proxy. Does this sound ok? @diracdeltas
cc: @jumde
How to Clean or upgraded profile?????
Any idea when we can get this feature back? Removing this is an absolute dealbreaker for most developers (including myself).
I feel like this was disabled for no good reason. At least let us decide if we want to download an extra package from Google but have it disabled by default.
@jumde this would be a great one for you to check out, when you have cycles 馃槃 (noticed you had already self-assigned). I think the big problem was that files are being fetched remotely. We can likely proxy those... and/or we could put this feature behind a flag
PR that disabled this: https://github.com/brave/brave-core/pull/790
Please re-enable remote debug :cry:
@rebron i think we should re-enable this with proxy (sorry for the delay)
actually enabling behind a flag would be fine if this is easier
I am a developer and will be switching back to chrome till there is a way for me to re-enable this. This breaks the Lighthouse Audit for me and who knows what else. I had previously been recommending Brave to other developers but not anymore. When I'm developing, I can't risk any issues coming from my tools and making debugging even more complicated.
This is an absolute deal breaker for any developer. Will be moving back to chrome and not recommending brave to any more developers till we can re-enable this.
+1. Please bring this feature back.
Taking a look at this now... I believe we'll be able to add a config flag for this (defaulted to OFF) which allows you to opt-in to the feature. I can make sure a clear log happens in case it's disabled (to make it more obvious). We'll need to have this go through security review too
Fixed! Will be in our next Nightly (1.3, which is due to ship Feb 4th). We may uplift to 1.2 (Dev, shipping Jan 6th) if there's enough support for it and if no problems are discovered 馃槃
I confirm that this works with Nightly 1.33.3 against a WebView running in React Native on a Nexus 6P device.
Thank you!
Adding QA/Blocked label per https://github.com/brave/brave-browser/issues/3199#issuecomment-567045246
Fixed in 1.2; waiting for a new BETA build before it can be tested again
Should be fixed in 1.2.30.
Verification passed on
Brave | 1.2.30 Chromium: 79.0.3945.79聽(Official Build)聽beta聽(64-bit)
-- | --
Revision | 29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916}
OS | Ubuntu 18.04 LTS
Verified using test plan from brave/brave-core#4044 for this issue.

Verification passed on
Brave | 1.2.37 Chromium: 79.0.3945.88聽(Official Build)聽beta聽(64-bit)
-- | --
Revision | c2a58a36b9411c80829b4b154bfcab97e581f1f3-refs/branch-heads/3945@{#954}
OS | Windows聽10 OS Version 1803 (Build 17134.1006)

Verified passed with
Brave | 1.2.40 Chromium: 79.0.3945.88聽(Official Build)聽(64-bit)
-- | --
Revision | c2a58a36b9411c80829b4b154bfcab97e581f1f3-refs/branch-heads/3945@{#954}
OS | macOS Version 10.14.6 (Build 18G103)
Before enabling Remote Debugging:

After enabling Remote Debugging:

Most helpful comment
Taking a look at this now... I believe we'll be able to add a config flag for this (defaulted to OFF) which allows you to opt-in to the feature. I can make sure a clear log happens in case it's disabled (to make it more obvious). We'll need to have this go through security review too