Problems I encountered while integrating about one_context HOT 4 CLOSED

Hi @YunhuiLiu140502 , sorry for the delay, I tried to reproduce the problem on my computer, but I couldn't.

Could you check if OneContext is being used elsewhere in the application before MaterialApp starts? You are probably trying to use some methods that will only be available after the first MaterialApp build.

OneContext needs to be initialized by MaterialApp before it can be used in the application. This error exception occurs when OneContext context has not yet loaded and you try to use some method that needs the context, such as the showDialog, dismissSnackBar, showSnackBar, showModalBottomSheet, showBottomSheet or popDialog methods.

If you need to use any of these OneContext methods before defining the MaterialApp, a safe way is to check if the OneContext context has already been initialized.

e.g. if (OneContext.hasContext) {OneContext ().showDialog (...);}

PS. All widgets below the MaterialApp have full access to the OneContext methods.

from one_context.

I’m closing this issue because of inactivity

from one_context.

I am getting same issue, @emanuel-braz please update on it.

from one_context.

Hi @maheshlalu , there is a reason to show this error, it's because the Flutter needs the context instance to be able to show dialogs. If there is no context, the lib can't do anything about that, unless, warn that something is wrong.

Solutions:

1 - Obviously, do not try show dialogs if there is no context available.(generaly this happens before the MaterialApp get mounted)

2 - If (for a specific reason) you not sure about if the context will be available. Please check it before.
e.g. if (OneContext.hasContext) {OneContext().showDialog(...);}

3 - Send a reproducible code, in order to I investigate deeply if there is a bug.

4 - If none of this works, you can do more for that, please send a PR that fix it. I'll thank you!

from one_context.