0.0.37-2 ionic build android --release doesn't build a new release! #279
Comments
I don't think the Thanks, |
@danbucholtz I read about --release on the forum regarding boot performances, that's why I was trying to use it actually. I guess it's kind of an inheritance of using it as in Ionic1 (see https://ionicframework.com/docs/guide/publishing.html). Personally I could leave without, was just really surprising that the thing was built, without errors of warnings, but that the result was the same previous version of my app without my fixes and enhancements. Thx for having a look |
@danbucholtz no pressure, but did you discover something about this subject "--release"? we had some conversations on the forum about boot time and AoT and @alfabetagama pointed out that he think that --release will generate the compilation of AoT aka when this option isn't use, AoT will not be included https://forum.ionicframework.com/t/ionic-2-speed-up-boot-time/46372/113 For the record, even I know --release may not be a valid option, tried again this one with 0.0.39 and I could reproduce the problem I reported above Sorry for asking, but I'm a little confuse about this issue, what does this options do or don't and when is really the AoT compilation done |
Hello! Thanks for using Ionic! So just to clear up any confusion, the use of the --release flag is not related in any way to if our build process uses AoT or not. When doing a |
thx @jgw96 and @danbucholtz all clear now. I think it makes sense to close that issue then, since --release isn't a thing, its side effect should also be ignored. |
except that ionic build android does a dev build with app-scripts 0.48, my understanding was: Serve / Emualate / Run are supposed to default to DEV But with the current version unless I use the --prod suffix I always get dev builds. It would be a good idea to note in the ionic update docs that --release is no longer used and the new way is to do ionic build android --prod instead. Otherwise everyone else trying to build a binary for the app store will either submit dev mode builds by accident (like I did) or end up spending an afternoon trawling the internet to find this random closed issue (also like I did). Hopefully this can save someone else some time. |
Please install the latest
sudo may or may not be required. Thanks, |
I can see how it can be a bit confusing with the different similar sounding flags. --release is actually a Cordova flag (the ionic command proxies arguments to the cordova command) telling the platform to do a release build (in iOS you can have different build settings dependent on if it's a debug or distribution build). |
I have the latest CLI installed already, behaviour is as I stated above. It's not that it's confusing so much as it's really not well documented anywhere. Maybe some docs somewhere on how to prepare a production release with examples? Ionic 1 had a similar section in the docs maybe that just needs to be updated to make these kind of changes clear |
Hey,
Is following command still a valid command?
If no, forget my message of course.
If yes, well, this command doesn't build anymore new releases.
I was working on version 0.6.4 of my app and was going to build 0.7.0.
I did the above command and deployed it on my phone. I noticed thensome weird bugs I just fixed and then noticed that the version number hasn't moved. Ran the commands and new installation from scratch, deleted the app to install it again, nothing changed, still same.
I then ran the build command without the argument --release aka
and I was then able to produce the right version of my app.
But as I said, maybe it's all my fault and that command doesn't exist at all, in such a case sorry for posting that issue.
The text was updated successfully, but these errors were encountered: