Navigation/routes fail to change when building capacitor app for iOS

Describe the bug When developing using capacitor on iOS application runs properly, but when built navigation fails to work. Once logged in I see the notification and changes in the drawer and nav bar, but the redirect to /home fails and no links in my drawer will work when clicked.

Codepen/jsFiddle/Codesandbox (required) I am prohibited from directly sharing code/repo by my employer, but can share any logs or details outside of such.

To Reproduce Steps to reproduce the behavior:

1. after installing capacitor, run quasar build -m capacitor -T ios --ide

Expected behavior Route should automatically change to /home once logged in. Navigation links should change views.

Screenshots If applicable, add screenshots to help explain your problem.

Platform (please complete the following information): Quasar Version: 1.15.3 and 1.15.4 @quasar/app Version: 2.1.14 and 2.1.15 Quasar mode: [ ] SPA [ ] SSR [ ] PWA [ ] Electron [ ] Cordova [x] Capacitor [ ] BEX Tested on: [ ] SPA [ ] SSR [ ] PWA [ ] Electron [ ] Cordova [x] Capacitor [ ] BEX OS: macOS 11.2.1 Node: 14.15.4 NPM: 7.5.4 Yarn: Browsers: iOS: 11.0 Android: Electron:

Additional context user g_holt at this link: https://forum.quasar-framework.org/topic/7843/capacitor-routes-won-t-change-when-building-ios-applicaiton said the following (I am unsure where he got this from, and may not be the case for me):

“I’m using router hash mode and on initial load the url is capacitor://localhost# instead of capacitor://localhost/#. So there is no trailing slash initially which breaks things. Sometimes when I navigate around this gets corrected. I tried setting PUBLIC_PATH=capacitor://localhost/ but it doesn’t seem to work.”

The only error I see within xcode is: 2021-02-22 13:40:45.122741-0500 App[12125:127986] API error: <_UIKBCompatInputView: 0x7fe4c85096a0; frame = (0 0; 0 0); layer = <CALayer: 0x6000022e0e00>> returned 0 width, assuming UIViewNoIntrinsicMetric.

[rstoenescu]

Glad that u figured it out!

[JonathanSloan]

My apologies, I have discovered that the issue was on my end and not yours. Another developer made changes involving routing that flew under the radar. Thank you for your assistance! Shall I close the issue, or you?