brave-browser: Developer tool doesn't load with remote devices in brave-browser (Desktop)
Test plan
See https://github.com/brave/brave-core/pull/4044
Description
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
Steps to Reproduce
- Clean or upgraded profile
- Connect Android device to Desktop
- Open
brave://inspect#devicesin Desktop - Visit a site on brave Android
- Ensure the site lists on brave://inspect#devices
- Click on
inspectunder the device name in desktop - Developer tool window launches but never loads
Actual result:
Developer tool window launches but never loads
Expected result:
Should load developer tool with remote devices
Reproduces how often:
Always
Brave version (brave://version info)
All brave versions
Version/Channel Information:
- Can you reproduce this issue with the current release? Yes
- Can you reproduce this issue with the beta channel? Yes
- Can you reproduce this issue with the dev channel? Yes
- Can you reproduce this issue with the nightly channel? Yes
Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? NA
- Does the issue resolve itself when disabling Brave Rewards? NA
- Is the issue reproducible on the latest version of Chrome? NA
Miscellaneous Information:
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 6
- Comments: 26 (8 by maintainers)
Commits related to this issue
- WIP - First steps towards solving https://github.com/brave/brave-browser/issues/5640 — committed to brave/brave-core by deleted user 5 years ago
- WIP - First steps towards solving https://github.com/brave/brave-browser/issues/5640 — committed to brave/brave-core by bsclifton 5 years ago
- Remote debugging can now be enabled via brave://settings/privacy Default for this is FALSE (meaning remote debugging is disabled). Setting is global (using local_state), not per-profile. Fixes https... — committed to brave/brave-core by bsclifton 5 years ago
- Remote debugging can now be enabled via brave://settings/privacy Default for this is FALSE (meaning remote debugging is disabled). Setting is global (using local_state), not per-profile. Fixes https... — committed to brave/brave-core by bsclifton 5 years ago
- Remote debugging can now be enabled via brave://settings/privacy Default for this is FALSE (meaning remote debugging is disabled). Setting is global (using local_state), not per-profile. Fixes https... — committed to brave/brave-core by bsclifton 5 years ago
- Remote debugging can now be enabled via brave://settings/privacy Default for this is FALSE (meaning remote debugging is disabled). Setting is global (using local_state), not per-profile. Fixes https... — committed to brave/brave-core by bsclifton 5 years ago
- Remote debugging can now be enabled via brave://settings/privacy Default for this is FALSE (meaning remote debugging is disabled). Setting is global (using local_state), not per-profile. Fixes https... — committed to brave/brave-core by bsclifton 5 years ago
- Remote debugging can now be enabled via brave://settings/privacy Default for this is FALSE (meaning remote debugging is disabled). Setting is global (using local_state), not per-profile. Fixes https... — committed to brave/brave-core by bsclifton 5 years ago
- Remote debugging can now be enabled via brave://settings/privacy Default for this is FALSE (meaning remote debugging is disabled). Setting is global (using local_state), not per-profile. Fixes https... — committed to brave/brave-core by bsclifton 5 years ago
- Remote debugging can now be enabled via brave://settings/privacy Default for this is FALSE (meaning remote debugging is disabled). Setting is global (using local_state), not per-profile. Fixes https... — committed to brave/brave-core by bsclifton 5 years ago
Very likely.
Checked it at Version 1.20.103 Chromium: 88.0.4324.152 (Official Build) (64-bit) And it’s not working.
Plus not able to find
Remote debuggingoption in flags of Brave desktop browser. MY OS - Ubuntu 20.04.2 LTSTaking 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
@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 ?
Checked Last version About Brave v 1.59.117
inspect fallbackif inspection fails.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 from Community https://community.brave.com/t/brave-remote-debugging-is-not-working/83109?u=eljuno
I confirm that this works with Nightly 1.33.3 against a WebView running in React Native on a Nexus 6P device.
Thank you!
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 😄
Please re-enable remote debug 😢
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.
We want to re-enable this by proxy. Does this sound ok? @diracdeltas cc: @jumde
Click on
inspect fallbackopens up devtool.