I want to show an AlertDialog when a http get fails. The function showDialog (https://api.flutter.dev/flutter/material/showDialog.html) has the parameter \"@required BuildContex
So you need a BuildContext
to create a dialog but you don't have access to it. That's a common problem, you can refer to this StackOverflow question for one of the approaches to solve it (create a static dialog and show it from wherever you need).
Another approach you may consider is to pass the context when creating an async method or object as an argument. Make sure you null it when you're done.
Or you can make a flag (boolean) which becomes 'true' under a certain condition, and in one of the build()
methods you always check that flag, and if it's 'true' - do your thing (show a dialog for instance).
The accepted answer is wrong.
The dialog only needs the context to access it through an inherited navigateState. You can make your own modified dialog, or use this lib to do this.
https://pub.dev/packages/get
With it you can open dialog from anywhere in your code without context by doing this:
Get.dialog(SimpleDialog());
Catch the exception where you make the getNews call if you use await, else use the catchError property of the Future.
Solution without third-party libraries or storing BuildContext
:
final navigatorKey = GlobalKey<NavigatorState>();
void main() => runApp(
MaterialApp(
home: HomePage(),
navigatorKey: navigatorKey, // Setting a global key for navigator
),
);
class HomePage extends StatelessWidget {
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(),
body: SafeArea(
child: Center(
child: Text('test')
)
),
floatingActionButton: FloatingActionButton(
onPressed: showMyDialog, // Calling the function without providing it BuildContext
),
);
}
}
void showMyDialog() {
showDialog(
context: navigatorKey.currentContext,
builder: (context) => Center(
child: Material(
color: Colors.transparent,
child: Text('Hello'),
),
)
);
}
After setting a global key for navigator (navigatorKey
parameter of MaterialApp
class), its current state becomes accessible from any part of the code. We can pass its context to the showDialog
function. Make sure not to use it before the first frame is built, otherwise the state will be null.
Basically, dialogs are just another type of routes like MaterialPageRoute
or CupertinoPageRoute
- they are all derived from the ModalRoute
class and their instances are pushed into NavigatorState
. Context is only needed to get the current navigator's state. A new route can be pushed without having a context if we have a global navigator key:
navigatorKey.currentState.push(route)
Unfortunately, _DialogRoute
class (...\flutter\lib\src\widgets\routes.dart) used in showDialog
function is private and unaccessible, but you make your own dialog route class and push it into the navigator's stack.
UPDATE: Navigator.of
method has been updated and it's no longer needed to pass subtree context.