Xamarin.Forms Shell Route Registration: Duplicate Route Key Behavior

Answer

Xamarin.Forms Shell navigation resolves a route key to the most recent Routing.RegisterRoute call for that key; the earlier mapping is silently overwritten and no exception is thrown in standard builds. This behavior has been observed consistently from Xamarin.Forms 4.x through 5.x+.

Confirmed facts

• The route dictionary is consulted at navigation time; if the key exists, the associated Page type is used.
• Calling RegisterRoute again with the same key replaces the previous entry immediately, even after Shell construction is complete.
• No documented API throws an exception for duplicate keys; only minor version‑specific changes or SDK conditions may emit a warning or ArgumentException.

Likely explanation

Because Shell’s navigation engine performs a simple lookup, the last registration wins. Dynamic re‑registration therefore updates the navigation map on‑the‑fly, allowing runtime route changes without restarting the app.

Steps to verify in your case

1. Create a minimal Shell project.
2. In the Shell constructor (or OnAppearing) register the same string twice with different Page types, e.g. Routing.RegisterRoute("demo", typeof(HomePage)) followed by Routing.RegisterRoute("demo", typeof(SettingsPage)).
3. Trigger navigation to the route using Shell.Current.GoToAsync("//demo").
4. Observe which Page is instantiated; the second registration should be the one displayed.
5. Inspect the Output/Debug window for any thrown exceptions or warning messages during the second RegisterRoute call.
6. Repeat the test on the exact Xamarin.Forms version you target (e.g., 4.8, 5.0, 5.1) to document any version‑specific differences.

If you need to know whether an exception is raised, specify the Xamarin.Forms version and whether the Shell is in the initialized or constructed state, as that can affect the outcome.