Created this issue: https://github.com/quasarframework/quasar/issues/8340 this github repo to reproduce: https://github.com/sluedecke/quasar-pwa-test

I solved this problem! I was specifying this in quasar.conf.js to fix some routing issues that I was seeing when running “quasar dev” : extendWebpack(cfg) { cfg.output = { publicPath: "/", }; } cfg.output was not set when running “quasar dev” but it is set when running “quasar build -m cordova -T ios” and so I was inadvertently overwriting it. Changing it to this let me get further: extendWebpack(cfg) { if (!cfg.output) { cfg.output = { publicPath: "/", }; } }

Maybe try resolve or path.resolve? extendWebpack (cfg) { cfg.resolve.alias = { ...cfg.resolve.alias, // Add your own alias like this 'vue$': 'vue/dist/vue.esm.js', '@': resolve('src') } or… extendWebpack (cfg) { cfg.resolve.alias = { ...cfg.resolve.alias, // Add your own alias like this 'vue$': 'vue/dist/vue.esm.js', '@': path.resolve('src') }

Updating Quasar to 0.17.6 solved the issue.

Hi sorry, I’m not sure whether this has been marked as resolved or not. Seems like I have same concern: So there will be 3 different environments (e.g: dev, staging, production). It will also have 3 different API url. (how to set these three up without using dot-env ext which failed in Amplify readability) It will have 3 different build commands. which one should I do first and how?

@mzamateo said in Deploy and upgrade quasar app: you can ask kindly to finish current work and then reload, with a popup or so… Exactly ! On my side, I put app version in localstorage (or cookie) and I check if the current version is different (ex: 9.0.10 -> 9.0.11) then I open dialog to inform the user that a new version is available since his last visit and if he want to see the changelog or not.

I’m glad you figured things out. Was about to contact you so I can take a look now, but you were faster