-
Notifications
You must be signed in to change notification settings - Fork 173
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
Navigator.pop #172
Comments
@sm2017 Have you found a solution? |
@SardorbekR No |
@sm2017 you can use toast in a provider , that will fix it |
@cmdrootaccess Can you show me a sample code for flushbar |
yes i will make an example in the next few hours and show you |
@cmdrootaccess Can you help me? |
sorry was busy. let me paste the code here. give me a moment |
create provider.dart . paste this
create toast.dart paste this.
create toast_widget.dart paste this.
Then in your main.dart do this . mind the AppProvider at the root instead of MaterialApp
then in home page or any other page you want to use the toast just call in the build block
example
|
@cmdrootaccess you are using |
I do have the same issue. Is there no out of the box solution from the library yet? For now I'm doing // Pop until you reach the dialog
Navigator.popUntil(
context,
ModalRoute.withName(AddPlaylistDialog.routeName),
);
// Pop the dialog itself
Navigator.pop(context); like also @sm2017 suggested, but it's not nice indeed. |
I have the same problem, my flushbar is hidden if I call .pop() in my app to hide modal windows and so on. I want flushbar to be always on the screen. Is there any solution? |
I am using flutter bloc in my application, is success response I call
Navigator.pop
to pop the navigator, and in failure I callFlushbar.show
to to toast error messageAs you push in navigator I have some problem, When I call
Navigator.pop
and the previous toast is exists in the page , it popped instead of the current pageI know I can use
Navigator.popUntil
, But I think it is the problem offlushbar
library, Because toast must not be a different routeThe text was updated successfully, but these errors were encountered: