Apparently this change is making this test fail because it changes how default routes are handled. It would be great if someone from the Angular team could comment on what the desired behaviour should be in this case.

@tiziano88 can you please provide

• a more explicit context for the error (perhaps a code example?)
• a unit test that demonstrates the bug being fixed

I am sure that we should not silently fail if a route is not found.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}