You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting navigatorKey: Get.key inside GetMaterialApp, the following exception occurs at runtime:
'''
Exception: GetRoot is not part of the tree
The relevant error-causing widget was: Builder(dirty)
'''
This issue disappears when navigatorKey: Get.key is removed. It seems that Get.key is not initialized correctly before being used in GetMaterialApp, leading to a navigation-related failure.
Steps to Reproduce:
Use navigatorKey: Get.key in GetMaterialApp.
Run the app.
The exception occurs immediately.
Expected Behavior:
navigatorKey: Get.key should work without causing the exception, ensuring smooth navigation handling.
Environment:
Flutter version: 3.24.3
GetX version:^5.0.0-release-candidate-9.2.1
Dart version: 3.5.3
Device/Platform: Android
Possible Workaround:
Using a manually created GlobalKey instead of Get.key resolves the issue. However, this should not be necessary when using GetX's built-in navigation system.
The text was updated successfully, but these errors were encountered:
When setting navigatorKey: Get.key inside GetMaterialApp, the following exception occurs at runtime:
'''
Exception: GetRoot is not part of the tree
The relevant error-causing widget was: Builder(dirty)
'''
This issue disappears when navigatorKey: Get.key is removed. It seems that Get.key is not initialized correctly before being used in GetMaterialApp, leading to a navigation-related failure.
Steps to Reproduce:
Use navigatorKey: Get.key in GetMaterialApp.
Run the app.
The exception occurs immediately.
Expected Behavior:
navigatorKey: Get.key should work without causing the exception, ensuring smooth navigation handling.
Environment:
Flutter version: 3.24.3
GetX version:^5.0.0-release-candidate-9.2.1
Dart version: 3.5.3
Device/Platform: Android
Possible Workaround:
Using a manually created GlobalKey instead of Get.key resolves the issue. However, this should not be necessary when using GetX's built-in navigation system.
The text was updated successfully, but these errors were encountered: