Unable to use history mode in Capacitor because `process.env.VUE_ROUTER_MODE` is not set to `'history'` in Android Capacitor mode.

[46319943]

What happened?

After setting vueRouterMode: 'history' in quasar.config, the SPA runs correctly in history mode. However, in Android Capacitor mode, the URL still falls back to hash mode.

While debugging with the Android WebView plugin in VS Code, I found that process.env.VUE_ROUTER_MODE is not set to history in Capacitor mode. As a result, the router defaults to createWebHashHistory in the defineRouter function inside router/index.ts.

What did you expect to happen?

process.env.VUE_ROUTER_MODE should be set to history as configured in quasar.config, so that the router uses history mode in Capacitor as well.

Reproduction URL

Note: The issue only occurs in Capacitor mode.

How to reproduce?

1. Set vueRouterMode: 'history' in quasar.config.
2. Run the app in Capacitor mode.
3. Use the remote debugger.
4. Observe that process.env.VUE_ROUTER_MODE is set to hash instead of history.

Flavour

Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)

Areas

Capacitor Mode

Platforms/Browsers

Android

Quasar info output

Relevant log output

Additional context

No response

[github-actions]

Hi @46319943! 👋

It looks like you provided an invalid or unsupported reproduction URL.
Do not use any service other than Codepen, jsFiddle, StackBlitz, CodeSandbox, and GitHub.
Make sure the URL you provided is correct and reachable. You can test it by visiting it in a private tab, another device, etc.
Please edit your original post above and provide a valid reproduction URL as explained.

Without a proper reproduction, your issue will have to get closed.

Thank you for your collaboration. 👏

[FragsterAt]

This is special workaround for capacitor and ios #17322 (comment)

[yusufkandemir]

Yes, thanks @FragsterAt

[46319943]

This is special workaround for capacitor and ios #17322 (comment)

@FragsterAt @yusufkandemir
Thank you for your quick response — it was really helpful and helped me understand the reason behind this. However, I think this should be explicitly stated in the documentation to avoid confusion. I’ve created a pull request to add this information: #18119.