quasarframework / quasar

Quasar Framework - Build high-performance VueJS user interfaces in record time
https://quasar.dev
MIT License
25.28k stars 3.43k forks source link

demo app run with a blank screen in iOS & Android with Vite #17057

Open landall opened 1 month ago

landall commented 1 month ago

What happened?

when I use npm init quasar to generate a new cordova app. if I choose option 1 (work with vite), the generate project will lead to a blank screen in ios & android, but spa mode works fine. if I choose option 3 (work with webpack), everything is ok.

node -v v16.14.2 vue -V @vue/cli 5.0.8 quasar -V @quasar/cli v2.4.0

What did you expect to happen?

Run in ios & android the same with spa in browser.

Reproduction URL

https://github.com/landall/cordova_demo_a/tree/ea2182b9054064613024878d1d75ae351448ff8e

How to reproduce?

  1. npm init quasar
  2. choose flavour with Vite stable. (option 1)
  3. quasar build -m ios (blank screen....)
  4. quasar dev run (everything is ok)

if choose webpack in step 2, everything is ok.

Flavour

Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)

Areas

Cordova Mode

Platforms/Browsers

iOS

Quasar info output

Operating System                Windows_NT(10.0.19045) - win32/x64
NodeJs                          16.14.2

Global packages
  NPM                           8.5.0
  yarn                          Not installed
  @quasar/cli                   2.4.0
  @quasar/icongenie             Not installed
  cordova                       12.0.0 (cordova-lib@12.0.1)

Networking
  Host                          CST-PC
  vEthernet (WLAN)              192.168.0.1
  vEthernet (Default Switch)    172.28.160.1
  WLAN                          192.168.31.13
  vEthernet (WSLCore)           172.24.160.1

Relevant log output

This commit is a test case.
I use CodeMagic as the compiler platform.
No ios signingCertificate.
the output is an app package for emulator, a unsigned ipa file for self-signing.
https://github.com/landall/cordova_demo_a/tree/ea2182b9054064613024878d1d75ae351448ff8e

Additional context

No response