Embedded DevTools window is empty with "Not found" message
See original GitHub issueWhen Dev Tools Location
is set to beside
or active
, the embedded DevTools window is empty with only a “Not found” message.
Steps to reproduce the behavior:
- In settings, choose
beside
oractive
as theDev Tools Location
option. - Start debugging
Expected behavior An embedded DevTools window containing widget trees information.
Screenshots
Please complete the following information:
- Operating System and version: macOs Monterey - version 12.4
- VS Code version: 1.68.0-insider
- Dart extension version: v3.42.1
- Dart/Flutter SDK version: Channel beta, 3.1.0
- Target device (if the issue relates to Flutter debugging): Any
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Chrome developer tools do not show all JavaScript files any ...
Solution: The fix for me was to copy the url address and paste it into a new tab and reopen dev tools. The...
Read more >ChromeDevTools connected to Inspector, but error responses ...
Chrome dev tools shows essentially an empty debugger, no sources, no console output, no errors... The responses my isolate/context sends back, suggest maybe ......
Read more >Reset Notion – Notion Help Center
Open the Developer Tools using cmd + option + i for Mac, or ctrl + shift + i for Windows. Keep the Developer...
Read more >Troubleshooting the Embedded Signup Form - Mailchimp
Learn how to fix common issues for embedded forms. ... My form shows no success or error messages. The embed form code ......
Read more >Use Chrome Developer Tools to check tags - Google Support
Select View > Developer > Developer tools. Available Tabs and their uses. Elements Tab: displays the page's rendered HTML, which is distinct from...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Great! I suspect some of the caching changes made in DevTools have probably resolved this particular issue then. I’ll close this, but if you (or anyone else) sees this again on >= Flutter 3.3 / Dart 2.18, please let me know.
I suspect once https://github.com/flutter/devtools/issues/3896 is solved this problem may go away, but I’ll keep this open for now to collect info in case there’s some additional going on when embedded in VS Code.