Network page does not show requests when running on Hyper-V
Problem description
The Network page of DevTools does not show network requests when running from within a Windows 11 VM Hyper-V virtual machine. Other hypervisors and operating systems have not been tested.
Steps to reproduce
- Run the example code on a bare-metal Windows 11 machine to verify the network request appears.
- Run the same code on a Windows 11 Hyper-V virtual machine and observe no network request appears.
Example code
import 'dart:io';
import 'package:flutter/material.dart';
void main() {
runApp(const MyApp());
}
Future<HttpClientRequest> load() async {
HttpClient client = HttpClient();
final HttpClientRequest response =
await client.get('tempapi.proj.me', 443, '/api/GB3XretjA');
return response;
}
class MyApp extends StatelessWidget {
const MyApp({super.key});
@override
Widget build(BuildContext context) {
return const MaterialApp(
home: MyHomePage(),
);
}
}
class MyHomePage extends StatelessWidget {
const MyHomePage({super.key});
@override
Widget build(BuildContext context) {
return Scaffold(
body: FutureBuilder(
future: load(),
builder:
(BuildContext context, AsyncSnapshot<HttpClientRequest> snapshot) {
if (snapshot.connectionState == ConnectionState.done) {
return Text('${snapshot.data}');
}
return const Text("Fetching...");
},
),
);
}
}
I'm going to keep an eye on this while working on some upcoming network stuff.
@hanskokx Much work has gone into the Networking tab over the last few years. I don't have access to Hyper-V so I don't think I can reproduce this without a sizeable effort. Do you know if you still face this problem with the latest stable or beta Flutter releases?
@hanskokx Much work has gone into the Networking tab over the last few years. I don't have access to Hyper-V so I don't think I can reproduce this without a sizeable effort. Do you know if you still face this problem with the latest stable or beta Flutter releases?
Just digging myself out from under a deluge of Github notifications and only now noticed this. I'll have to go back and test to see.
Closing this as not reproducible. Feel free to re-open if you are still seeing this problem and can provide some debugging information for us to investigate. Thanks!