@sebag well, late to the party, but you could do something like…

          actions: [
            {
              icon: 'close',
              color: 'white',
              handler: () => {},
            },
          ],

and your css could be…

.q-notification__actions .q-btn__wrapper.col.row.q-anchor--skip {
  padding: 0px !important;
  font-size: 8px !important;
}

.q-notification__actions .q-btn__wrapper.col.row.q-anchor--skip i {
  position: absolute;
  top: -10px;
  font-weight: bold;
}

I just solved the issue (in my case “not working anymore” meant that I kept getting 404 error) this way:

quasar.conf.js

devServer: {
    ...
    // add this:
    historyApiFallback: {
        disableDotRule: true,
  },

Reference: https://webpack.js.org/configuration/dev-server/#devserverhistoryapifallback

Well, I faced the same necessity. In my case, with buttons inside a <q-toolbar>, I was able to workaround the issue as follows.

From this

<q-btn stretch flat :to="{ name: 'items' }" label="Items" />

To:

<q-btn stretch flat label="Items">
  <router-link
    exact
    :to="{ name: 'items' }"
    class="absolute full-width full-height"
  ></router-link>
</q-btn>

Style:

.router-link-active {
  border-bottom: 2px solid white;
}

me too, thanks.

@keepingitsimple any result? I’d also need to use a cropper and wonder what it could be an easy way to integrate it. Thanks.

@dsky https://forum.quasar-framework.org/topic/2481/quasar-quasar-cli-v0-17-aka-ssr-developer-preview/

Quasar 0.17 refactors how the back button is handled. Please test this version (beta).

cordova: {
  iosStatusBarPadding: true/false, // add the dynamic top padding on iOS mobile devices
  backButtonExit: true/false // Quasar handles app exit on mobile phone back button
}

@liuzhongshu @dsky related https://github.com/quasarframework/quasar/issues/1897

@koohsaran70 yes, for me it was enough; the emulator is running on your local machine, so sharing the same ip. I’m sorry, I work on Linux and have no experience on Windows, but I don’t think this is the point.

Btw, in the log you should check/filter for cordova errors, where a Vue stacktrace should appear.

I’m out of other ideas, hope someone will chip in.

@koohsaran70
You could:

1. Check that your phone and your PC reside on the same network (eg 192.168.0.x)
2. If you use a firewall/antivirus, allow traffic between PC <–> phone
3. Attach a log viewer to your phone and check for error messages

For 3. I use superlog (https://github.com/wangfei1975/superlog)

The log reads:

No target specified and no devices found, deploying to emulator

CordovaError: No emulator images (avds) found.

and goes on with:

1. Download desired System Image by running…
2. Create an AVD by running…

Did you do these steps?

@polger Oh LOL my memory… http://forum.quasar-framework.org/topic/565/quasar-minification-with-babili/5

I had the same. I think, this is why

Uglify cannot parse ES6, it will throw you syntax errors. Either set TypeScript to target ES5, post-process your generated JS with babel, or use a different minifier.

I don’t remember details, but the issue was caused by some js package not really “compatible”. Again IIRC I managed to fix the issue tweaking the build process using this https://github.com/webpack-contrib/babel-minify-webpack-plugin.

If there is any expert in this field (I’m not), please chip in and help. Thank you.

Ok, weirdo. I tried to install the plugin in a “base” quasar project and everything works with no errors. By “base project” I mean: answer no to all the questions at quasar init phase, especially don’t use a linter (I really think this is the point…).

Then I created project2 answering yes to all, and got the same your issue:

/tmp/project2/src/pages/index.vue
  24:18  error  'FileTransfer' is not defined  no-undef

✖ 1 problem (1 error, 0 warnings)

In project2 then I tried to disable the linter… and everything worked as expected (I disable the linter commenting the body of extendWebpack (cfg) in quasar.conf.js, not sure if it’s the right way but the linter was disabled).

index.vue:

<template>                                                                                                                         
  <q-page class="flex flex-center">
    <div>
      {{ foo }}
    </div>
    <img alt="Quasar logo" src="~assets/quasar-logo-full.svg">
  </q-page>
</template>

<style>
</style>

<script>
export default {
  name: 'PageIndex',
  data: function () {
    return {
      foo: ''
    }
  },
  created: function () {
    this.foo = FileTransfer
  }
}
</script>

Well, hope this gives you some help. Let us know.

@jaz basically signing the apk should solve the issue. Would you please check this? http://forum.quasar-framework.org/topic/1979/installed-apk-generated-by-quasar-dev-build-command-does-not-work-in-android

don’t crosspost http://forum.quasar-framework.org/topic/2142/build-problem-stuck-in-apache-cordova-ready/

don’t crosspost http://forum.quasar-framework.org/topic/2143/stuck-apache-cordova-device-ready-screen

@rstoenescu worth to add it to the docs?

@ksathya yep!!! my earlier update confirms that! (sorry for not mentioning you). http://forum.quasar-framework.org/topic/1979/installed-apk-generated-by-quasar-dev-build-command-does-not-work-in-android/6

@ksathya said in Installed apk generated by quasar dev / build command does not work in Android:

When I use ‘build for production’ command (quasar build -m cordova -T android -t mat) and try to copy the apk generated, the device says ‘App cannot be installed’.

Hey same here. Were you able to make it run and how do I see logs on the phone?

The command I run (I don’t see any error message during the process):

$ quasar build -m cordova -T android -t mat

Update:
I was able to fix my issue signing the apk as described in the docs. Not sure if I hijacked this thread, apologies if this happened.