bug: ionic vue cannot route to shared url with param

[milleniumfrog]

Bug Report

Ionic version:

[ ] 4.x
[x] 5.x

Current behavior:
Ion Router Outlet does not display shared urls, if they contain params.
If the shared urls do not contain params it works as expected.

Expected behavior:

Shared urls should always work, even when route params are used

Steps to reproduce:

Reproduce Error

• create shared urls with a param
  e.g. /a/:message and /app/:message/test
• navigate to /app/:message/test without reloading the page

Sample Application

• Clone this repository: https://github.com/milleniumfrog/ionic_router_bug
• yarn install
• yarn run serve
• visit localhost:8080
  Then use the buttons to navigate to PageA (Page with route params) -> PageA1. (Should fail)

**Related code:**

<!-- If you are able to illustrate the bug or feature request with an example, please provide a sample application via one of the following means:
https://github.com/milleniumfrog/ionic_router_bug

[liamdebeasi]

Thanks for the issue. Can you try the following dev build and let me know if it resolves the issue?

npm install @ionic/[email protected] @ionic/[email protected] --save-exact

[milleniumfrog]

The dev package solves the issue 👍 .

[milleniumfrog]

I found a new related bug.

When using route parameters the routing only works the first time. If the same route is used with an other parameter routing stops working for this route

.

I updated the ionic bug sample app https://github.com/milleniumfrog/ionic_router_bug

[liamdebeasi]

@milleniumfrog Did you push your changes? I only see the package.json change.

[milleniumfrog]

@liamdebeasi yes i forgot to push the changes. I updated it now.

[liamdebeasi]

Thanks! Can you try this dev build? It should fix the issue:

npm install @ionic/[email protected] @ionic/[email protected] --save-exact

[milleniumfrog]

The update fixed the problems 👍.

[liamdebeasi]

Thanks for checking! I am going to keep this issue open until #22360 gets merged in.

[liamdebeasi]

Thanks for the issue. This has been resolved via #22360, and a fix will be available in an upcoming release of Ionic Framework.

[ionitron-bot]

Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out.