Cordova undefined on iOS

[s.molinari]

Cool! Hope you let us in on its release (if possible)!

Scott

[Martin]

@s.molinari Surely I will.

[Martin]

@rstoenescu Is it possible to get a branch from v12.0 with the cordova fix? Or maybe just the code snippet (if it’s an easy fix)
Some Modals and popups don’t seem to work with yesterday’s quasar-edge.
(haven’t tried today)
thanks.

[rstoenescu]

@Martin oh? I’m really interested in what the problems are. Wanna release v0.13 this or next week (depending on how much time I have). Skipped v0.12.1 because edge version contains sooo many novelties and enhancements.

[Martin]

@rstoenescu ok, I’ll try again today with latest edge and see if I can give you something reproducible.

[Martin]

I’m getting a null error when closing a Modal. After that it’s not possible to open it again.
I’ll try to set up a simple example that reproduces this.

[Martin]

At first I thought it was related to my cordova security settings, but that’s fixed.
Now I’m only getting this error
"TypeError: Cannot read property ‘removeChild’ of null
at VueComponent.beforeDestroy "
The same error also appears with PopOvers.
Searching on Google gave me this link (a vue-material issue with md-tooltips)
with similar error.
https://github.com/marcosmoura/vue-material/issues/188

[rstoenescu]

@Martin Ok, now I know what’s this about. Can you share your repo to see the exact use case of your Modal pls? A private link or something. You’re on an edge case and I’d like to fix that also. Thanks!

[Martin]

Ok I’ve set up a rep for you. What email address can I send the link to?

[rstoenescu]

razvan.stoenescu@gmail.com

[rstoenescu]

Oops, “The owner of this repository (skilldance) is already at their plan limit and will need to upgrade before adding more users.”

[rstoenescu]

Ok, discussed with Martin in private. He helped me reproduce his use case and pushed fix for it. Quasar edge has it and v0.13 (next immediate version) will too.

[rstoenescu]

Quasar v0.13 is out so this is fixed.

[Gianni]

I got the same Cordova error here.

I installed quasar-framework v0.13

What i was trying is to use this plugin :
window.cordova.plugins.insomnia.keepAwake()

I also tried to call it without window
cordova.plugins.insomnia.keepAwake()

Cordova is wrapped and the JS files are located at the right place
./cordova/platforms/android/assets/www/cordova.js
./cordova/platforms/android/platform_www/cordova.js
./cordova/platforms/ios/CordovaLib/cordova.js
./cordova/platforms/ios/platform_www/cordova.js
./cordova/platforms/ios/www/cordova.js

It does not work in the Browser nor in the Play App.
I ran the quasar with this command : PORT=9000 quasar dev mat -p

Is there a way to check if cordova got included properly? Or do i need to import or initialise it somehow ?

[Gianni]

[rstoenescu]

Cordova is not accessible in the browser on your desktop. It must be run from an actual cordova app. As for viewing your app in Quasar Play, due to technical limitations you won’t be able to access “cordova” global. This is documented at the bottom of the page here: http://quasar-framework.org/guide/quasar-play-app.html

IMPORTANT. While playing with your App in Quasar Play, Cordova functionality will currently not be available. This is due to Cordova Javascript code causing a crash in its Java container.

What you need to do is build your app, wrap it with cordova and run in on an actual device. Doing this will give you access to the “cordova” global. Also make sure that in the cordova wrapper folder you install the cordova plugins that you use.

[Gianni]

Thank you for your help!

ah ok … that makes sense now. It would be grate to place this note on the cordova wrapper site too.
I hope it will be available one time, since i have to uncomment all cordova plugin calls to develop in my browser.

So on my device i have access to the cordova object now. i call the plugin as follow :
window.plugins.insomnia.keepAwake()
this crashes the browser with : Uncaught TypeError: Cannot read property ‘insomnia’ of undefined

Bit it works on my Hardware. The phone keeps awake.

interesting: this call causes no problems at all in the browser.
navigator.vibrate(300)

[rstoenescu]

Navigator Vibrate causes no problems because it’s a Web API: https://developer.mozilla.org/en-US/docs/Web/API/Navigator/vibrate