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
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Run the app normally and check debug logs
Expected behavior
There should be no errors regarding keys and global keys must be used on individual widgets only once
Actual behavior
Some widgets are inserted in the widget tree multiple times causing Multiple widgets used the same GlobalKey error. This doesn't crash the app, but still is bad and causes problems in testing.
Screenshots
Additional details
During testing, I found out that this issue comes from explore_events.dart file with this key assignment, along with other pages used in MainScreen Widget
The problem is that navBarItems is first initialized with all the BottomNavigationBarItem, but some of these items are again added to the list in the renderBottomNavBarPlugins method.
Fix
Removing duplicate BottomNavigationBarItem addition fixes the problem
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
There should be no errors regarding keys and global keys must be used on individual widgets only once
Actual behavior
Some widgets are inserted in the widget tree multiple times causing
Multiple widgets used the same GlobalKey
error. This doesn't crash the app, but still is bad and causes problems in testing.Screenshots
Additional details
During testing, I found out that this issue comes from
explore_events.dart
file with this key assignment, along with other pages used in MainScreen WidgetThe problem is that
navBarItems
is first initialized with all theBottomNavigationBarItem
, but some of these items are again added to the list in therenderBottomNavBarPlugins
method.Fix
Removing duplicate
BottomNavigationBarItem
addition fixes the problemI would like to know if this issue is hitting multiple people. @palisadoes @noman2002 @CyberWake @Ayush0Chaudhary
The text was updated successfully, but these errors were encountered: