Multiple widgets used the same GlobalKey when nesting VNesters

[momrak]

Issue type: Question
Platform: Web

I have an app which produces this when trying to add a nested nesters. I assume this might be related to this #77 (comment) ? I have also seen other issues here mentioning roughly the same, but I still don't really understand why this happens.

Do you have a general explanation for these kind of issues? I am trying to wrap my head around navigation in Flutter, so might be that I have completely misunderstood my issue as well :) hehe

[VRouter: INFO] Successfully navigated to "/family/fid1234/person/pers123/prop/prop123/prop2/prop1234" using VRouter.to �[0m
nesten builder 1
nested builder 2
nesten builder 1
nested builder 2
nested builder 2
nested builder 2
══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
The following assertion was thrown while finalizing the widget tree:
Multiple widgets used the same GlobalKey.
The key [LabeledGlobalKey<NavigatorState>#96b66 VNesterPageBase of name null and key null
navigatorKey] was used by multiple widgets. The parents of those widgets were different widgets that
both had the following description:
  Builder
A GlobalKey can only be specified on one widget at a time in the widget tree.

The first time I go to the path this works, but when navigating to new path where only some of the pathparams from the first path has been updated I get what you see here. Even though there is only one Successfully navigated to... entry it enters the builder two times.

[peazz]

Currently getting this as well,

let’s say I go to /route/:routeId/dashboard where routeId is 123.

if I context.vRouter.to(‘/route/345/dashboard’) I get the same error and my screen goes blank where the view should loads.

Clearly; the nester is is trying to load the same view and not assigning a new key despite the route changing and a new instance of the class existing.

[rohitranjan1991]

@lulupointu any fix or workaround for this ??

[lulupointu]

Sorry about this issue I must have missed it.

This is certainly an issue with the key that sometimes has to be used in VNester.
Could someone produce a small reproducible example so that I can easily help you?