For anyone else with this issue, I found the reason. Since I replaced the src folder entirely, I missed the fact that due to changes in vue-loader (https://github.com/vuejs/vue-loader/releases/tag/v13.0.0), the main quasar start was being called differently. Once I replaced:

Quasar.start(() => {
  /* eslint-disable no-new */
  new Vue({
    el: '#q-app',
    router,
    render: h => h(require('./App'))
  })
})

with

Quasar.start(() => {
  /* eslint-disable no-new */
  new Vue({
    el: '#q-app',
    router,
    render: h => h(require('./App').default)
  })
})

Everything started working again.

OMFG!!! I have a solution!!!

1. I add a check for versionstring on the server, and return it to the app.
2. I look for it in localtstorage (IndexedDB) and if I don’t find it, I add it. If I do find it, I compare versions and if there is a newer one on the server, I throw up a dialog.
3. Dismissing this dialog (my ok button is labeled “update”) runs window.location.reload(true) and then stores the new versionstring in localstorage

RESULT: My app is updated!! I have been searching for a way to do this for weeks and weeks, so glad it finally works on iOS. Hope this helps someone else.

And thanks for fixing Ouch! No more errors!

Can anyone point me to any guide for getting my PWA to update automatically for users when there are changes or a new version? Is there anything in Quasar built in to help accomplish this? Currently (on iOS at least) users need to clear their Safari cache in order to have the PWA reload its data, a not very intuitive or UI-friendly thing to do. I have been looking around the web and it seems like maybe I have to customize the service-worker.js to check some version variable and invalidate the cache? Is this the right way to go or something else?

I have been reading the docs here (https://v1.quasar-framework.org/style/typography) and although I see the section on adding custom fonts, is there not a way to simply replace the default Roboto in all cases with another font (I am thinking of Open Sans)?

@rstoenescu thanks, but I didn’t want to remove it and then have to recreate every place it was used, I just wanted to replace it with another font and keep all the same settings for all the same weights, locations, etc.

sure, here is my boot file:

// for when you don't specify quasar.conf.js > framework: 'all'
import { Quasar } from 'quasar'
import { i18n } from 'boot/i18n.js'

export default async ({ store }) => {
  let previouslyRestored = false
  await store.restored
  if (!previouslyRestored) {
    previouslyRestored = true
  }

  let langIso = 'en-gb'
  if (previouslyRestored) {
    console.log(store.state.rstruth.lang_prefs)
    if (store.state.rstruth.lang_prefs !== 'en-gb') {
      langIso = store.state.rstruth.lang_prefs
    }
    i18n.locale = langIso
    try {
      await import(`quasar/lang/${langIso}`)
        .then(lang => {
          Quasar.lang.set(lang.default)
        })
    } catch (err) {
      // Requested Quasar Language Pack does not exist,
      // let's not break the app, so catching error
    }
  }
}

Some important things to note:

• This relies on a vuex store and a way to persist my vuex values (I use vuex-persist but there are other ways)
• I am using a call in vuex-persist (previouslyRestored) to check if my state has been restored before I try to access values from the store.

Does anyone have any tips for getting Cordova to use WKwebview? I have tried various official and unofficial plugins, but when they are installed, my app then refuses to make an API call and login. When I am using the old UIwebview it works but is slower…

@RishitKedia would you mind describing in a very high level, brief way how you used quasar to build this, and then how you implemented/integrated that work to make this extension? I am just really curious what the steps would be, and how quasar could even be used for this. Thanks!

try setting the row height in the global table config.

patientConfigs: {
        rowHeight: '50px'
}

Well, after heading over to github and doing a lot of searching, I seem to have found reference (if not a solution) to the problem here:

https://github.com/quasarframework/quasar/issues/7272

Hope this helps someone else.

After much testing, I have narrowed this down and it is always reproducible for me with the following steps:

1. quasar create newproject
2. During setup choose all the defaults (the only deviation for me was choosing npm instead of yarn in the last step)
3. cd newproject
4. quasar dev -m pwa
5. Open chrome devtools, make sure “Bypass for network” is selected in “Application”/“Service Workers” tab
6. From project folder open src/Index.vue and make any small change (I just removed the quasar img) and save file

RESULT: Quasar hot reloads with error, and in the dev tools console of chrome, the following message will be displayed one or more times:

GenerateSW has been called multiple times, perhaps due to running webpack in --watch mode. The precache manifest generated after the first call may be inaccurate! Please see https://github.com/GoogleChrome/workbox/issues/1790 for more information.

Because this is a brand new project coming from quasar create, it seems highly unlikely to be related to any project changes I could have made. Here is the result of the quasar info command for that folder:

Operating System - Darwin(19.5.0) - darwin/x64
NodeJs - 12.18.1

Global packages
  NPM - 6.14.5
  yarn - Not installed
  @quasar/cli - 1.1.0
  cordova - Not installed

Important local packages
  quasar - 1.12.8 -- Build high-performance VueJS user interfaces (SPA, PWA, SSR, Mobile and Desktop) in record time
  @quasar/app - 2.0.1 -- Quasar Framework local CLI
  @quasar/extras - 1.8.2 -- Quasar Framework fonts, icons and animations
  eslint-plugin-quasar - Not installed
  vue - 2.6.11 -- Reactive, component-oriented view layer for modern web interfaces.
  vue-router - 3.2.0 -- Official router for Vue.js 2
  vuex - 3.4.0 -- state management for Vue.js
  electron - Not installed
  electron-packager - Not installed
  electron-builder - Not installed
  @capacitor/core - Not installed
  @capacitor/cli - Not installed
  @capacitor/android - Not installed
  @capacitor/ios - Not installed
  @babel/core - 7.10.4 -- Babel compiler core.
  webpack - 4.43.0 -- Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
  webpack-dev-server - 3.11.0 -- Serves a webpack app. Updates the browser on changes.
  workbox-webpack-plugin - 5.1.3 -- A plugin for your Webpack build process, helping you generate a manifest of local files that workbox-sw should precache.
  register-service-worker - 1.7.1 -- Script for registering service worker, with hooks
  typescript - 3.9.5 -- TypeScript is a language for application scale JavaScript development

Quasar App Extensions
  *None installed*

Networking
  Host - iMac
  en1 - 192.168.10.22

Unless I hear some specific advice from someone here, I guess I will report this in github. But it really surprises me that no one else has experienced this, which makes me think that it could be something in my computer setup, but no idea what that could be…

NOTE: I recreated this post from an earlier one and deleted that one for clarity, only leaving the absolute minimum necessary to understand the issue and not to confuse things with my troubleshooting progress.

to be a little clearer (hoepfully), if I remove iconSet: 'fontawesome-v5-pro', and boot: ['fontawesome-pro'] from my quasar.conf.js file, quasar’s built in components will no longer show any icons. Originally I wanted to replace those with JUST the svgs/icons I am using, nothing more, to reduce the built bundle size. Because if we look in the boot file for the iconset, quasar is including:

// required
import '@fortawesome/fontawesome-pro/css/fontawesome.min.css'
import '@fortawesome/fontawesome-pro/css/light.min.css'
// do you want these too?
// import '@fortawesome/fontawesome-pro/css/brands.min.css'
// import '@fortawesome/fontawesome-pro/css/solid.min.css'
// import '@fortawesome/fontawesome-pro/css/regular.min.css'

Which seems to bundle the entire light iconset, NOT just the ones that are used in the components I have built and or chosen from the built in ones.

@qyloxe not sure I am understanding you, but I am just talking about the webfont icons, so it should be possible to only load the ones I am using in my design (with svgs). Visitors/Users don’t use webfont icons other than to view the ones that are set. It seems that the entire iconset is being included in the build whether or not they are being used, but perhaps I am mistaken?

I mean, if one can’t replace the webfonts used in the components, and one is using icons from that same webfont elsewhere, does that mean there is no reason to use SVGs at all? The built project seems to include the entire webfont, not just the used ones…

I have poured over the documentation for svg (https://quasar.dev/vue-components/icon#Svg-icons) and iconsets (https://quasar.dev/options/quasar-icon-sets#Configuring-the-default-Icon-Set) but don’t see a way to replace the icons used by quasar components with svgs. And if I can’t do that, it does not seem that I am significantly reducing my bundle size, since I am using the same icons (fontawesome pro) for all my icons and it seems necessary to include it in my quasar.conf.js file. I have tested importing my own defined svgs and using them for q-btn and q-icon and it works fine. But I can’t figure out how to replace the iconset with svg instead of the webfont.

@metalsadman I think that explains a lot. So if that boot file is included in the conf file, I should no longer have to do an import axios from 'axios' in any file I use axios in? (and instead of writing my calls as axios.get I should be able to use this.$axios.get everywhere?)

After rereading the boot file docs (https://quasar.dev/quasar-cli/boot-files), and looking at my /src/boot folder, I see files that are not in the boot: [] area of quasar.conf.js, but still seem to be working (axios.js among them). Did something change in recent versions and should I make sure any file that is in the boot folder have a corresponding entry in boot: [] area of quasar.conf.js?