No More Posting New Topics!

@pankaj I have gotten it working already.

cordova plugin add cordova-plugin-purchase.

Here is my boot file:

import productIds from '../utils/productIds'; export default ()=>{ if(process.env.MODE!=='cordova')return; if(!window.store){ console.log('Store not available'); return; } store.validator='https://validator.fovea.cc/v1/validate?appName=...&apiKey=...'; productIds.forEach(id=>{ store.register({ id, type:id.endsWith('_single')?store.CONSUMABLE:store.PAID_SUBSCRIPTION }); store.when(id).approved(product=>product.verify()).verified(product=>product.finish()); }); store.error(error=>{ console.log(error); store.refresh(); }); store.refresh(); };

And in my store component page I just call

store.order(product);

I also used PayPal for the equivalent purchases in electron.

@daveshirman

Page transition animations
Comes out of the box in Quasar, not sure about Ionic Easy of customising CSS
In Quasar you have SASS, SCSS and Stylus variables. Ease of making a production build on iOS and Android
I’ve only ever done Android. It works seamlessly. Compatibility with Cordova/Capacitor
Fully compatible but I think for Capacitor Ionic may have an edge since they wrote Capacitor after all. General feel of the app Vs native
Perfect for Android (material design), but Quasar got rid of its iOS mode so you have to configure the UI elements manually. I hope they bring it back. Job opportunities
Here’s where we lose out, I guess. But we have the jobs board on this forum and the jobs channel on Discord. Tooling stability
There was a major shift from CLI v1 to v2 which resulted in many changes having to be made and there’s no automated migration tool (yet). However, if you’re starting out fresh you’ll start with CLI v2. Real apps I can check out.
Check out my apps at https://customautosys.com/covidgame and https://customautosys.com/ketoshare.

@realtebo they are available when your app is created.

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

Never mind… instructions are changed: https://quasar.dev/quasar-cli/developing-cordova-apps/preparation

I must install manually gradle now.

No problem.

Same issue in here. I would like use q-file or q-uploader, but in apk or in browser the behavior is different. In Browser show “chose an action” for select camera or files, but in apk not, files are selected whitout chosen an action.

I installed plugins and permissions, but continue not working.

Your server should handle the cors, not your frontend.

I reinstalled node with nvm and it worked.

For mor details, have a look at https://stackoverflow.com/questions/59973611/node-js-child-process-has-no-access-to-global-modules

I solved it by adding

plugins: ["@babel/plugin-transform-modules-commonjs"]

to babel.config.js

@wwwizzarrdry could you give code example pls? i was try using example code from documentation that plugin, but still not working

After searching around the XDA forums, there isn’t any mention of how to do this there either.

Same thing with the Cordova github documentation.

Am I to believe that in 2019, Android has no official capacity in it’s filesystem to mount samba shares? And if it does, why is there no documentation for it anywhere?

I think this app has already been stopped being supported.

I solved this problem!

I was specifying this in quasar.conf.js to fix some routing issues that I was seeing when running “quasar dev” :

extendWebpack(cfg) { cfg.output = { publicPath: "/", }; }

cfg.output was not set when running “quasar dev” but it is set when running “quasar build -m cordova -T ios” and so I was inadvertently overwriting it.

Changing it to this let me get further:

extendWebpack(cfg) { if (!cfg.output) { cfg.output = { publicPath: "/", }; } }

If you are interested in updating to Babel 7.x (which I have done), there is a great tool here: https://github.com/babel/babel-upgrade

The way it used to be was a namespace for your company and app name. So if my company’s name was Acme and the app is “Delivery Box”, I’d probably enter com.acme.delivery-box. Digging around in the documentation I found this: cordova create myapp com.mycompany.myteam.myapp MyApp on this page: https://cordova.apache.org/docs/en/9.x/reference/cordova-cli/index.html#directory-structure.

Updating Quasar to 0.17.6 solved the issue.

For babel polyfill, just tamper with the .babelrc – mind that for v0.16+ u’re on Babel 7, not 6

has this been fixed in V1 beta too? In beta4 you still have hack quasar.conf.js to get https working for Cordova .

This is most likely a cordova issue.