I solved it using webpack copy plugin in this post. https://forum.quasar-framework.org/topic/2472/robots-txt-in-root/5

in quasar.conf.js file

const CopyWebpackPlugin = require('copy-webpack-plugin');
/// ...
extendWebpack(cfg) {
   cfg.plugins.push(new CopyWebpackPlugin([{ from: 'src/myCustomFolder/', to: '' }]));
  /// ...
}

Update:

Create a dir “myCustomFolder” in src dir and copy my firebase-messaging-sw.js into “myCustomFolder”

https://forum.quasar-framework.org/topic/2472/robots-txt-in-root/5

Great work!

I’m new on Mac OS and I try to launch capacitor app in IOS mode but this say me a error

(node:863) UnhandledPromiseRejectionWarning:   TypeError: Expected a `target`

  - index.js:25 module.exports
    [real-state-app]/[open]/index.js:25:9

  - open-ide.js:27 runMacOS
    [real-state-app]/[@quasar]/app/lib/helpers/open-ide.js:27:5

  - open-ide.js:166 module.exports
    [real-state-app]/[@quasar]/app/lib/helpers/open-ide.js:166:14

  - index.js:50 CapacitorRunner.run
    [real-state-app]/[@quasar]/app/lib/capacitor/index.js:50:11

  - runMicrotasks

  - task_queues.js:93 processTicksAndRejections
    internal/process/task_queues.js:93:5

(Use `node --trace-warnings ...` to show where the warning was created)
(node:863) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 7)
(node:863) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

$ quasar dev -m capacitor -T ios

I have Mac OS Catalina (10.15.7) and Xcode 12.4

@beets Thanks a lot!!! you are my hero!

I have an array of objects and I would like to mark the checkboxes that are already inside my array "selected:

Example code;

  data () {
    return {
      selection: [ {name: 'teal'}, {name: 'red'} ]
    }
  }

<div id="q-app">
  <div class="q-pa-md">
    <div class="q-gutter-sm">
      <q-checkbox
          v-for="(option, index) in options"
          v-model="selection" 
          :val="option"
          :label="option.label"
          :color="option.label"></q-checkbox>
    </div>

    <div class="q-px-sm">
      The model data: <strong>{{ selection }}</strong>
    </div>
  </div>
</div>

What am I waiting for?

What’s going on ?

Example: https://codepen.io/itsalb3rt/pen/oNYZNrZ?editors=101

Solved, changed on /src-capacitor->android->app->build.gradle only need change the versionCode and versionName found on https://stackoverflow.com/a/22274740/8009061

The basic problem is the capacitor build version, not changed when try chante it on /package.json or set this on /quasar.conf.js->capacitor->version.

No matter what you do it stays in version 1.0

I try change this to version 2.0.0 or any other.

Google play console cancels my upload because it says that I already have an application with version 1.

@ngekoding Yes, read my last comment

Fixed, the problem is the messaging.usePublicVapidKey() firebase method, I was not verifying that the browser supports this function.

// src/boot/firebase.js
let messaging = {}

if (firebase.messaging.isSupported()) {
  messaging = firebase.messaging()
  messaging.usePublicVapidKey(process.env.PUBLIC_VAPI_KEY)
}

@beets no error in console

@beets Now that I remember after adding firebase cloud function for push notifications to project I happen this.

firebase-messaging-sw.js

// Give the service worker access to Firebase Messaging.
// Note that you can only use Firebase Messaging here, other Firebase libraries
// are not available in the service worker.
importScripts('https://www.gstatic.com/firebasejs/7.17.2/firebase-app.js')
importScripts('https://www.gstatic.com/firebasejs/7.17.2/firebase-messaging.js')

// Initialize the Firebase app in the service worker by passing in
// your app's Firebase config object.
// https://firebase.google.com/docs/web/setup#config-object
firebase.initializeApp({
  messagingSenderId: '',
  projectId: '',
  apiKey: '',
  appId: ''
})

// Retrieve an instance of Firebase Messaging so that it can handle background
// messages.
const messaging = firebase.messaging()

@beets Yes, in SPA mode it also fails.