Unexpected onDelete called just after Get.toNamed(), controller deleted. #1360
Replies: 6 comments 3 replies
-
I am facing the same problem. Is there any solution available? |
Beta Was this translation helpful? Give feedback.
-
Use Flutter bloc/cubit.
…On Tue, 10 Aug 2021 at 16:14, flutterwithfaiz ***@***.***> wrote:
I am facing the same problem. Is there any solution available?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1360 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGFYZXXGBGSTISUDLWBLJKTT4D7ILANCNFSM43P6IJ2A>
.
--
With Warm Regards,
*MOHD ASIF*,
LinkedIn: https://www.linkedin.com/in/techieasif
|
Beta Was this translation helpful? Give feedback.
-
You should call Get.find on the very first screen on your app, so GetX will not delete it: |
Beta Was this translation helpful? Give feedback.
-
try this permanent: true |
Beta Was this translation helpful? Give feedback.
-
Hi, I had the same bug but in my case, I used |
Beta Was this translation helpful? Give feedback.
-
you first need to persist the controller by calling it on the main method like
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm just navigating to new page using named routes, as soon as toNamed trigged new screen flashed, then closed console shows 'onDelete called', REPLACE ROUTE with navigating one.
NOTE: Navigating to NewTaskPage(),
New task page flashed and then the console shows this:
Please help.
@jasonlaw
Beta Was this translation helpful? Give feedback.
All reactions