Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

bug: vue, back button not finding correct route info

See original GitHub issue

Prequisites

I have read the Contributing Guidelines.
I agree to follow the Code of Conduct.
I have searched for existing issues that already report this problem, without success.

Ionic Framework Version

v4.x
v5.x
v6.x

Current Behavior

The back button stops working under certain scenarios

Expected Behavior

The back button should work

Steps to Reproduce

Clone the linked repo
ionic serve
Click Topics > Topic 1 > Article 1
Click the back button (not the browser back button) to get back to Topics
Click Topics > Topic 2 > Article 1 or Article 2
The back button will no longer work

Code Reproduction URL

https://github.com/GC-Mark/testing-app

Ionic Info

Ionic:

   Ionic CLI       : 6.17.1 (/usr/local/lib/node_modules/@ionic/cli)
   Ionic Framework : @ionic/vue 5.8.1

Capacitor:

   Capacitor CLI      : 3.2.3
   @capacitor/android : not installed
   @capacitor/core    : 3.2.3
   @capacitor/ios     : not installed

Utility:

   cordova-res : 0.15.3
   native-run  : 1.4.1

System:

   NodeJS : v15.14.0 (/usr/local/bin/node)
   npm    : 7.24.1
   OS     : macOS Big Sur

Additional Information

https://user-images.githubusercontent.com/1477806/134936973-44a7acf0-4fdb-4e6e-b96d-04119329b967.mov

Issue Analytics

State:
Created 2 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

liamdebeasicommented, Oct 13, 2021

Thanks for the issue. This has been resolved via https://github.com/ionic-team/ionic-framework/pull/24060, and a fix will be available in an upcoming release of Ionic Framework.

Feel free to keep testing that dev build and let me know if you run into any issues. Thanks!

1reaction

GC-Markcommented, Oct 13, 2021

I have checked the specific problem in our app and can confirm that #24060 seems to have fixed the issue 👍