SOLVED

Just FYI to whoever read this. After try & error I found that different platform has different behaviour when handling “accept” attribute.
What I did for QUploader & QFile to set accept props value from computed:

<q-uploader :accept="accept"> or <q-file :accept="accept">

export default{
  computed: {
    accept () {
      return this.$q.platform.is.cordova ? 'image/*' : '.jpg, .jpeg, .png'
    }
  },
}

based on this https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/file#Unique_file_type_specifiers I have tried use one of them (just extension or MIME) or combine file extension and MIME type but none of them were working. Have to use one option based on platform

@metalsadman I have tried before and all states in the store are undefined, except if I re-init project with included store

Hi All,
Regarding this question https://forum.quasar-framework.org/topic/1953/adding-a-store-vuex-later I still don’t get the answer.
How to solve this problem properly instead of re-init new project like what I do if I want to init/add vuex store later (don’t get me wrong, it’s not quasar new store store_name). Doing like what I did is non-sense

I have solved it. Read it here https://forum.quasar-framework.org/topic/6951/solved-quploader-qfile-on-android

SOLVED

Just FYI to whoever read this. After try & error I found that different platform has different behaviour when handling “accept” attribute.
What I did for QUploader & QFile to set accept props value from computed:

<q-uploader :accept="accept"> or <q-file :accept="accept">

export default{
  computed: {
    accept () {
      return this.$q.platform.is.cordova ? 'image/*' : '.jpg, .jpeg, .png'
    }
  },
}

based on this https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/file#Unique_file_type_specifiers I have tried use one of them (just extension or MIME) or combine file extension and MIME type but none of them were working. Have to use one option based on platform

Hi guys,

I use QUploader for Cordova development. On web/desktop mode, “plus” icon QUploader can open file browser, but when I build it to Android with Cordova, “plus” sign can’t open file browser.
Did I miss configuration or some code lines?

I face the same problem as well. There’s a solution on here https://github.com/quasarframework/quasar/issues/776.
I found the file location is in src-cordova\platforms\android\app\src\main. I have tried put the code lines mentioned on the solution above but it still didn’t work. I don’t know did I edit the wrong/correct xml file but still didn’t work either.

thank you @s-molinari for the clear explanation!

I have same confusion with @realtebo

from this documentation https://quasar.dev/quasar-cli/app-upgrade-guide#Introduction said that quasar/app and quasar are different packages (one is the Quasar App CLI and one is the Quasar UI), each one with its own version.
Currently Quasar is v1.14.1 , quasar/app is v2.1.1 and quasar/cli is v1.1.2

based on documentation above, what is the difference between cli and app since those two said the same but have difference version (v1.1.2 and v2.1.1)? and I guess Quasar is the components and related with UI right?

Thank you for the explanations @dobbel and @metalsadman

Hi guys,

I made custom boot file and want to have axios in it. I found that $axios object comes from “store” parameter code bellow

export default async ({ app, router, store, Vue }) => {
    console.log('store from custom boot file', store)
}

just wondering:

1. why does $axios (and $router as well) come from store and not from “app” or “Vue” (or “router”) parameter?
2. what is the difference $axios & $router from store and “regular” this.$axios & this.$router from vue file?
3. If I want to use $axios in my boot file just straight forward store.$axios.get("/path") or do I need to import?

import axios from 'axios'

btw Quasar Framework is really awesome! I loved it from the first time I knew it