-
Notifications
You must be signed in to change notification settings - Fork 326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flutter debugging network view displays only socket request issues #8518
Comments
Ask an off topic question,May I ask why there have been no new builds for releases since 2020? |
#8502 |
https://github.com/xhc-code/my_flutter_network_problem.git The code here includes both HTTP and sockets when using Dio to request linked data. Moreover, the number of socket and get requests is not equal. The request for Image.network network images is not displayed in the network view. |
Having the same issues with using http package on latest Flutter 3.24.4. |
Same issue here, it looks like they don't mind the broken system. They are more focused on other things than making something important work... :-( |
@kenzieschmoll Can you check this please? Looks like it's completely broken for lots of people. Thanks! |
same here , |
What is actually requested in the picture https://cdn.pixabay.com/photo/2023/09/25/20/138/lisbon-8275994_1280.jpg Request, but in Flutter's debugging network, it shows a socket request and cannot see the parameters of the request and response. May I ask why this is?
We are using Flutter>version 3.4.1 and the Dio: ^ 5.4.3+1 request library.
The actual requests sent are all HTTP or HTTPS, but all the requests displayed in the socket are socket requests. I don't know where the problem lies because the socket is clearly not used.
Using an Android emulator
Image.network("https://cdn.pixabay.com/photo/2023/09/25/20/138/lisbon-8275994_1280.jpg", width: 50, height: 50,),
This is the image component that makes the request, and requests made using the Dio library are also socket requests displayed on the network.
The text was updated successfully, but these errors were encountered: