Uncaught exception in FutureBuilder, is it normal? - flutter

Question

If I throw an exception in a Future, and use such future in a FutureBuilder, the debugger warns me about it being "uncaught". Is this by design or am I using FutureBuilders wrong?
My scenario is a typical one: show a loading spinner while data is retrieved from an HTTP API. I do so through the following (simplified) code:
class MyWidgetState extends State<MyWidget> {
Future<String> getSomeText() async {
// Just throw an exception here to simulate a network error
throw Exception("Network error");
}
#override
Widget build(BuildContext context) => FutureBuilder(
future: getSomeText(),
builder: (context, AsyncSnapshot<String> snapshot) {
if (snapshot.connectionState == ConnectionState.done) {
if (snapshot.hasError)
return Text("Got an error");
return Text(snapshot.data);
}
else
return CircularProgressIndicator();
}
);
}
When I draw this widget, the Network error exception is thrown and my debugger (I use VSCode with the official Flutter plugin) halts execution and shows it to me. If I then chose to continue execution, the app behaves as expected.
Reading around a bit, I thought that happens because getSomeText() gets called and completes BEFORE the builder is even created, and the builder's exception handlers do not have time to register with the future. However, using Future.delay() to introduce a delay results in exactly the same behavior.
I also tried to execute such code in one of Flutter's documentation code boxes, and there it apparently works without throwing exceptions. Is it simply ignoring it as it is thrown into a Future?
I wonder if such exception should be caught (as I expect) or not? Is leaving it uncaught in this scenario a Flutter design choice?