Closed w0pp closed 1 week ago
By the way @rstoenescu is there a reason why Quasar assumes you're building for an emulator, not a device? AFAIK Cordova also supports building for a device with the --device
Cordova CLI option.
I'll take care of everything. In the mean time, one can always directly use the IDE to build. Call the quasar build cmd with "--ide" argv (it will open the IDE where you can build & extract the distributable yourself)
In fact, it's already built, it just fails at the very last step of copying files to /dist.
Fix will be available in q/app-vite 1.8.4 & 2.0.0-beta.10 and q/app-webpack 3.12.7 & 4.0.0-beta.11
And released all of them.
Thanks for the quick response! Though I'm not sure why you added --device
to the Cordova CLI options. Doesn't that essentially make it impossible to build for simulators?
Besides, the build doesn't always output to platforms/ios/build/Release-iphoneos
- it can also output to any of these paths:
platforms/ios/build/Release-iphonesimulator
platforms/ios/build/Debug-iphoneos
platforms/ios/build/Debug-iphonesimulator
@w0pp Impossible is a strong word. You can always use the IDE to build directly (--ide param), or skip the build process entirely (--skip-pkg) and manually run any command (or run a script from quasar.config > build > afterBuild).
Added the "--device" param because this is something that can easily be missed (for some reason Cordova choses to build for the simulator by default) by unexperienced developers. However, please take a look at https://github.com/quasarframework/quasar/commit/8a4034c53dcf7b1363e44dfcfcabe96d5059524d and comment if you feel the need. I think this will nail it for whatever use cases there are out there, even for future cordova-ios/android versions (until we can pick it up and add native support).
What happened?
When running
quasar build -m ios
, the build fails when Quasar tries to copyplatforms/ios/build/emulator
to thedist/
folder. This is becausecordova-ios@7.0.0
changed the location of where the output files are generated - see the release notes.What did you expect to happen?
Build should not fail.
Reproduction URL
/
How to reproduce?
Flavour
Quasar CLI with Webpack (@quasar/cli | @quasar/app-webpack)
Areas
Quasar CLI Commands/Configuration (@quasar/cli | @quasar/app-webpack | @quasar/app-vite), Cordova Mode
Platforms/Browsers
iOS
Quasar info output
Relevant log output
Additional context
Normally there's no error printed in the log - had to manually catch the webpack() promise exception inside
build.js
and output it.