This is exactly what I was looking for, thanks for the reply!

I am curious how quasar-framework.org converts the markdown text on github to what is displayed on the website?

I really like how the md is nicely integrated into the website. Is a standard library used? Is there any reference code available?

Any help is appreciated.

Thanks!

The https option appears to be disabled for cordova and electron builds, commenting out ‘cfg.devServer.https = false’ in <project>/node_modules/quasar-cli/lib/quasar-config.js eveything works:

  if (this.ctx.mode.cordova || this.ctx.mode.electron) {
    // cfg.devServer.https = false
    cfg.devServer.open = false
    cfg.devServer.compress = false
  }

Chrome requires an https domain to access the media APIs.

The last comment of this post:
https://github.com/quasarframework/quasar/issues/701
Seems to indicate that https is now supported.

I see quasar 0.15.14 has a ‘https’ option in the ‘dev’ section of the quasar.conf.js. However, setting it to ‘true’ doesn’t seem to have any effect after running:
quasar dev -m cordova -T browser

Does anyone have any pointers on how to enable https for the dev server?

@LaurentPayot What was your setup?

Following the instructions here:
https://firebase.google.com/docs/auth/web/cordova

Using Quasar-0.15.14

and running:
quasar dev -m cordova -T android

It seems to be redirecting the dev server URL in a new browser window (rather than the actual app).

Running:
const provider = new firebase.auth.GoogleAuthProvider()
self.auth.signInWithRedirect(provider)
return self.auth.getRedirectResult()

opens a new browser to the google oauth page, but then redirects to the dev server URL (instead reopening the app).

I strongly suspect this has to with the way Quasar does hot reload (which fricking awesome btw!).

If I run:
quasar build -m cordova -T android

Then download the app, .auth.signInWithRedirect(provider) works as expected.

Does anyone know how to do OAuth in a cordova dev build on android?