Open CarlosBernalA opened 1 year ago
Note that this modification partially solved the problem.
@jonataslaw , @CarlosBernalA This issue only exist in unNamed routing. I tried Named routing and it's working properly
Define route like this in GetMaterialApp
initialRoute: '/',
getPages: [
GetPage(name: '/', page: () => Splash()),
],
Where you want to navigation write this code
Get.offNamed('/');
OR
Get.toNamed('/');
@mohsinnaqvi606 Even so, the problem persists, this happened after updating Flutter to version 3, before that there was no problem, I attach images of the initialization of the routung of my app.
When calling Get.back() or another back method it only shows this message in the console, before it eliminated memory
@mohsinnaqvi606 Even so, the problem persists, this happened after updating Flutter to version 3, before that there was no problem, I attach images of the initialization of the routung of my app.
When calling Get.back() or another back method it only shows this message in the console, before it eliminated memory
@CarlosBernalA Yes, you are right. It's working only in few cases. It's hard to understand, what is the cause of issue. My suggested solution worked in one project. but it's still not working in other project
You're right. I had the same problem
same issue
When navigating to a route with Get.toName takes you to the route correctly, but when leaving the route with Get.Back or any other means the state of the route remains and when entering the route again it remains with the previous state, The Controller continues with the same state as the previous one, it does not die at any time, it is still in memory.
A few months ago I was forced to make some modifications to the get code, temporarily while another version comes out, but the modification was simple but I am not sure it is the correct change. The change I made was to the router_observer.dart file in the didPop event. Below I attach a screenshot, maybe it will help:
Getx Version: get: ^4.6.6