Chapter 11. Deploying Your Application
Now with your application fully tested, it is time to create the versions that can be submitted to the various app stores. Before we generate the release build of our app, we should remove any assets that should not be included in our production release.
For example, the Console plug-in was added when we first generated our Ionic application, so let’s remove it from our installed plug-ins. To do this, simply run:
$ ionic cordova plugin remove cordova-plugin-console
We also need to manually delete the reference to this plug-in in our config.xml file. Locate this line and delete it:
<plugin name="cordova-plugin-console" spec="~1.0.4"/>
Adjusting the config.xml File
Before generating your production build, you may also need to adjust the config.xml file with some additional settings. By default, the config.xml that is generated by Ionic is fairly bare bones. There are many additional settings you may wish to configure for your application, such as restricting the OS versions your app will run on. Other items within the config.xml that you may want to adjust can include the version number, restricting the domain access list, and replacing development API endpoints with production API endpoints.
For a summary of these settings, see Appendix B or the full documentation at the Cordova website.
App Icons and Splash Screens
If you have not already replaced the stock icons and splash screens that are included when you use the Ionic templates, ...
Get Mobile App Development with Ionic, Revised Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.