Solved… read the doc. …

// import something here
import { Platform } from 'quasar'

export default async (/* { Vue } */) => {
  if (!Platform.is.mobile) {
    return
  }

We resolvede server side on development using a proxy bypass with origin rewrite. For production server we’re unable to enable origin ‘*’ so we’ll try to add a reverse proxy or a pass through proxy like done in development.

Thanks

I’ve a q-scroll-area with some paraph inside. But it shows nothing. It’s zero pixel heigh.
What’s the trick with this component, exsential when developing for mobile?

We resolvede server side on development using a proxy bypass with origin rewrite. For production server we’re unable to enable origin ‘*’ so we’ll try to add a reverse proxy or a pass through proxy like done in development.

Thanks

I a new boot file I’ve the need to use both a cordova plugin and axios.

Is there a way to be sure that axios and cordova plugins are really available before trying to use them?

Solved… read the doc. …

// import something here
import { Platform } from 'quasar'

export default async (/* { Vue } */) => {
  if (!Platform.is.mobile) {
    return
  }

I’m initializing a db using a cordova plugin.

I’d like in the boot to detect if app is running on mobile, before even try to open db.

I tried the following

export default async ({ Vue }) => {
  if (!Vue.$q.platform.is.mobile) {
    return
  }
...

But Vue.$q is undefined here

Could I ask what is app v2?

Aren’t we at 1.14?

Hi !

I’ve the need to handle some time (and resource) consuming background task in our app.

I’ve the need to allow user to navigate from page to page, but having a little indicator on the top [in the main layout file] that show progression of what is happening behind scenes.

The problem is not here.

The problem is HOW to keep a long task running in background in a quasar app.

I could use a boot file to start the task, but I need to avoid UI blocks.

If any, could you sdhare with me any suggestions?

I understand it’s most server side. But I cannot understand why quasar app has this problems while native java android app has not problem doing requests to web services.

I’m developing a web app since a while. Now we’re tring to run it as a mobile app (android only in this moment).

We stopped becase all api calls from mobile app is being blocked because of cors policy.

I’ve not a clear idea of how cors headers and preflight options calls works.

Anyway, I ask you kindly if there is something from quasar app code side to be done to be able to make api calls.

I never faced problem in calling apis using native java android apps. I stupidly thinked it wil not be a problem in a quasar cordova mode app.

Please, help me to understand what should I do to allow my app to make api calls.

Damn… Turn Off and Turn On … First rule of IT …

I resolved simply doing …

cd cordova-src
cordova platform remove android
cordova platform add android

I am on windows 10

Running quasar dev -m cordova -T android

I got this

DONE  Compiled successfully in 18249ms                                                                          9:50:30

i ｢wds｣: Project is running at http://192.168.20.43:3000/
i ｢wds｣: webpack output is served from
i ｢wds｣: 404s will fallback to /index.html

App · Updated Cordova config.xml
App · Running "cordova run android"

No Java files found that extend CordovaActivity.

App · Command "cordova" failed with exit code: 1
App · Updated Cordova config.xml
App · ⚠️  [FAIL] Cordova CLI has failed

What is this?