@larskuerten You are right i can see it in chrome, I’ll get back to you

I found in another thread you posted that the IE Support might need to be added… I am trying that now… but it seems like I was on Quasar v1 all along? You can use compositional API with quasar v1? I am so new I didn’t know what to look for.

@s-molinari that seems to do the trick. I am terrible at front end too, but you are further along than me! Thanks!

Ah…You are trying to do environment variables.

You need this extension: https://www.npmjs.com/package/@quasar/quasar-app-extension-qenv

You’ll make a separate .quasar.env.json.

I made a workaround / hack for now on iOS with this line on my initial page.

created(){ if(this.$q.platform.is.ios){ this.window.location = "capacitor://localhost/#/" } }

At least that solves the urgent issue for now and sets the trailing slash correctly to “/#/” for all subsequent navigations.

I’ve had the same problem.
I’ve changed the order of the imports and now it works.

Some Details
This was the error message:

chunk chunk-common [mini-css-extract-plugin] Conflicting order. Following module has been added: * css ./node_modules/css-loader/dist/cjs.js??ref--8-oneOf-2-1!./node_modules/vue-loader/lib/loaders/stylePostLoader.js!./node_modules/postcss-loader/src??ref--8-oneOf-2-2!./node_modules/sass-loader/dist/cjs.js??ref--8-oneOf-2-3!./node_modules/@quasar/app/lib/webpack/loader.quasar-scss-variables.js!./node_modules/@quasar/app/lib/webpack/loader.auto-import-client.js?kebab!./node_modules/vue-loader/lib??vue-loader-options!./src/components/TimerProgress.vue?vue&type=style&index=0&lang=scss& despite it was not able to fulfill desired ordering with these modules: * css ./node_modules/css-loader/dist/cjs.js??ref--8-oneOf-2-1!./node_modules/vue-loader/lib/loaders/stylePostLoader.js!./node_modules/postcss-loader/src??ref--8-oneOf-2-2!./node_modules/sass-loader/dist/cjs.js??ref--8-oneOf-2-3!./node_modules/@quasar/app/lib/webpack/loader.quasar-scss-variables.js!./node_modules/@quasar/app/lib/webpack/loader.auto-import-client.js?kebab!./node_modules/vue-loader/lib??vue-loader-options!./src/components/Booth.vue?vue&type=style&index=0&lang=scss& - couldn't fulfill desired order of chunk group(s)

You see: “Booth.vue” at the end of the message. So I searched for files where I import Booth.vue. I’ve opened the file and changed

<script> import userflap from '../components/Userflap.vue'; import connectoor from "../components/Connectoor.vue"; import Booth from '../components/Booth.vue'; ...

to

<script> import Booth from '../components/Booth.vue'; import userflap from '../components/Userflap.vue'; import connectoor from "../components/Connectoor.vue"; ...

So the only difference is the import order (“import Booth” is now at first place).
And now it worked again without setting “ignoreOrder”.

In meantime i google this issue : https://github.com/quasarframework/quasar/issues/4835
but no solution from this thread worked for me
so im sure that it’s not definitely network problem . it is problem with packages

@Adagio - wow, that v-money Codepen looks pretty powerful. I have similar headaches with decimal numbers - though in my app those are not currencies, but geometrical heights.

But I still have to digest how I could make use of this v-money stuff. At a first glance, the code looks very different from my current code, as I don’t even see q-input fields in the Codepen. It wraps a native HTML input field (v-money directive) or a new component (v-money component) within a q-field, rather than using a q-input as usual for data entry. I never used q-field, but at a first glance it seems to have the same or nearly the same props a q-input, so the conversion is hopefully not too difficult.

What worries me a bit playing with that Codepen for v-money is this “right to left” data entry (same as “reverse fill mask” in Quasar). That could be found unusual by users. used to normal Quasar q-inputs without reverse fill mask. Do you know whether it can be changed?

@gorgc I don’t think it has rules like text inputs, but you can always validate the value yourself.

II was able to just use Q-radio’s and ditch getting it with data via v-for, its a totally static 2 option thing that’ll probably never change, so just putting it in the HTML doesn’t seem too terrible.

I’m having the same issue with @LIANG-FENG and @bruno-ronchetti
It uploads perfectly to Firebase. But I don’t have a url.
I tried moving from async await syntax to Promise syntax. It didn’t work.
I tried removing all the events from the quploader, except for the @factory-failed event. It didn’t work.
It gives error, but the thing works.

don’t use http2 on non-SSL ports