[Blazor] Fix null reference exception caused by ambiguous routes #39833
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When two Blazor routes are ambiguous the generated exception is obfuscated by following attempts to access the route table.
The reason this happens is that we update the route key before we compute a new table, and when the table fails, the next time we try the key, we return null.
The solution is to wait to set the key until we've successfully computed the route table to avoid hiding exceptions in that case.