Nevermind, just seen In the docs It’s not supported yet https://quasar.dev/quasar-cli/developing-capacitor-apps/capacitor-version-support
Posts made by jadedRepublic
-
RE: CAPBridgeViewController.swift not found or content is unrecognized (HTTPS / Capacitor V3 issue)
-
CAPBridgeViewController.swift not found or content is unrecognized (HTTPS / Capacitor V3 issue)
After upgrading to Capacitor V3, I’m getting the above error when In dev. Any suggestions on a fix for this?
-
RE: openURL in current tab
@JSONK I’ve removed all my previous suggestions as It was getting confusing, my original suggestion for using a button does what you need It to do. I just got tag & type mixed up.
<q-btn type="a" href="https://quasar.dev/">Quasar</q-btn>
-
RE: Access Capacitor API from store action ?
@Marin-Vartan Is there any reason not to install It separately outside src-capacitor?
-
RE: CAPBridgeViewController.swift not found or content is unrecognized - Please disable HTTPS from quasar.conf.js > devServer > https
So In node_modules -> @quasar -> app -> lib -> capacitor -> capacitor-config.js, there Is a function called __handleSSLonIOS() that resolves the file “node_modules/@capacitor/ios/ios/Capacitor/Capacitor/CAPBridgeViewController.swift” however on @capacitor 2.4.0, the path Is “node_modules/@capacitor/ios/Capacitor/Capacitor/CAPBridgeViewController.swift”
Current quasar version is 1.12.13
-
CAPBridgeViewController.swift not found or content is unrecognized - Please disable HTTPS from quasar.conf.js > devServer > https
Can anyone help with the below error?
Disabling HTTPS In quasar.conf hides the terminal error but I’m just stuck on the splashscreen (I think It’s loading scrips via https).
Below works fine with PWA mode, and initially worked without any issues when running dev on IOS with capacitor. Quasar creates an external dev server when I run quasar dev -m capacitor -T ios which when I open, does not show any SSL errors.
devServer: { https: { key: fs.readFileSync('ssl/server.key'), cert: fs.readFileSync('ssl/server.crt'), }, port: 8080, open: true // opens browser window automatically },
In Xcode, I get the following errors:
️ WebView failed provisional navigation
️ Error: The certificate for this server is invalid. You might be connecting to a server that is pretending to be “192.168.1.117” which could put your confidential information at risk.
-
RE: q-loading and scollIntoView
Did you add to your plugins In Quasar.conf? plugins: [‘Loading’]
-
RE: Sharing my social sharing dialog component
@qyloxe said in Sharing my social sharing dialog component:
https://quasar.dev/quasar-utils/other-utils#Copy-to-Clipboard
Does copy to clipboard have support for all platforms? I’ve been using Capacitor since It’s already in my project but didn’t realise Quasar supports It
-
RE: How to use transitions between routes?
@Tinny I’m fairly certain that’s how the layout Is intended anyway In Quasar, I personally make page specific changes to my layout header using $route.name, you can change what Is visible and what Isn’t like this:
<template> <q-header> <component :is="component.name" v-for="(component, index) in components" :key="index" v-if="$route.name == component.route"/> </q-header> </template> <script> export default { data () { return { components: [ { name: 'AboutActions', route: 'about', }, { name: 'ContactActions', route: 'contact' }, { name: 'ShopActions', route: 'shop', }, ] } }, components: { AboutActions: () => import("./Includes/About"), ContactActions: () => import("./Includes/Contact"), ShopActions: () => import("./Includes/Shop"), }, } </script>
-
RE: error in router
Btw I would recommend using localforage, here Is an example:
import localforage from 'localforage' export default { methods: { apilogin (login) { return new Promise((resolve, reject) => { var response = { data: { token: 'Token', loggedIn: 'loggedIn', name: 'Name', image: 'Image', id: 'ID', employeeid: 'Employeeid' } } resolve(response) }) }, login () { return this.apilogin({ email: 'john@doe.com', password: 'doe123' }).then((response) => { return localforage.setItem('token', response.data).then(() => { return localforage.getItem('token').then((token) => { commit("setUserDetails", token); this.router.push({ name: 'index' }); }).catch((e) => console.log('Failed to get storage tokens: ' + e.toString())) }).catch((e) => console.log('Failed to set storage tokens: ' + e.toString())) }) } } }
-
RE: error in router
this.$router.push({ name: ‘index’ }); does that give you an error?
-
RE: access the store
import { firebaseAuth, firebaseDb } from "boot/firebase"; import { axiosInstance } from "boot/axios"; const state = { TOKEN: null, loggedIn: false, userDetails: {}, loading_login: false, currentPage: { title: "", IsActive: false }, CONFIGSYS: { COMPANY_ID: 0 } }; export default state <-- Add this at the bottom
-
RE: error in router
Are you doing anything else with your router like a beforeeach?
-
RE: How to use transitions between routes?
I would recommend having a second router view, one for all of your main pages and the transition for all child pages of a main page e.g.
<router-view/> <router-view name="popup" v-if="$route.meta.popup"/> // Add your css transition or use a dialog
Routes
{ path: '/home/', component: () => import('layouts/default.vue'), children: [ { path: '', component: () => import('pages/Home/index.vue'), name: 'home', meta: { popup: false, }, }, { path: 'about', name: 'about.popup', components: { default: () => import('pages/Home/index.vue'), popup: () => import('pages/About/index.vue') }, meta: { popup: true, }, }, ] },
-
RE: Capacitor and SplashScreen
@ramsesmoreno Is It showing 2 different splash screens by any chance? I vague remember getting the same error, I just tried a fresh install of Quasar and It work as expected without changing anything