Network response tab fails to build

[CoderDake]

#2860 (comment)

Shows a grey box in the response tab which means there may have been an error building the response tab.

[CoderDake]

@VanLong-official could you please provide some more information about the issue you are having?

• Does the response tab ever get to a better state?
• If you "Toggle Developer Tools", do you seen any errors that pop up when you reproduce this?
  • 
• Is there anything special about the requests you are trying to inspect?

Any other information would be greatly appreciated

[merenyimiklos]

@CoderDake hey, i have the same issue, not grey screen, just the last error still have, no response data in the response page

[CoderDake]

@merenyimiklos fascinating :O
Could you please try toggling the vscode developer tools to see if there are any errors showing up in the console?

[merenyimiklos]

@CoderDake no error in the debug console, or in the output, so don't know this

[CoderDake]

@merenyimiklos if I was to put together a special DevTools branch, with detailed logging, would you be open to reproducing this so that I can get a more in depth Idea of what is going on behind the scenes?

[merenyimiklos]

@CoderDake sure we can try, but can you add me on skype and tutorial me what i need to do do? :D

[CoderDake]

It looked like merenymiklos wasn't on the right version of Devtools. which may have contributed.

[DarrellBrogdon]

I'm having the same problem. I'm running Dart DevTools version 2.20.1.

Attached is my VSCode with the console.

[CoderDake]

@DarrellBrogdon Could you please try this again with the master channel of flutter? It has some fixes pertaining to the network tab.
to change your flutter channel you can use
flutter channel master
If you run your app with that version, then you should get access to the new version, Devtools 2.22.1.

[DarrellBrogdon]

That works... kind-of. The first GET request I ran worked but the second is showing a gray box.

[CoderDake]

@merenyimiklos @DarrellBrogdon If you would like to try out the new logging behaviour I'm getting ready, you can try out the following:

1. Clone the flutter/devtools repo
2. checkout the network-logging branch
3. Change your flutter to master using flutter channel master; flutter upgrade
4. cd devtools/packages/devtools_app
5. flutter pub get
6. flutter run -d chrome
7. Once Devtools open up you should be able to connect to your app.
8. Click on the settings at the top right

9. Enable the verbose logging setting.

10. Next click the clear button beside the "enable verbose logging" setting
    

11. Now go reproduce the behaviour

12. after reproducing, come back to the settings and click the copy button beside the logging setting

13. check to make sure there is no sensitive information.

14. then you should be able to upload those logs here, hopefully it will help point out what is going wrong.

[CoderDake]

@DarrellBrogdon unfortunately there is nothing we can do to accelerate Devtools through the master, beta and stable channels.

Until the changes make it through to stable, you may just need to flip to master while doing network debugging. (Assuming we can get this stuff working smoothly for everyone)

[merenyimiklos]

@CoderDake i will wait for this, and until i will work with Android if i need network table i guess... :D

how long is it take to take the feature to the stable channel?

[CoderDake]

Oh oops sorry for pinging you About the master channel stuff Darrell I was supposed to ping in a different issue about that.

[CoderDake]

@merenyimiklos I believe that changes are made to the stable channel once per quarter. So about once every three months

[CoderDake]

I believe this issue should be fixed in #5327

We are doing a release in the next coming weeks so it should make it to the next flutter beta.