We have a Meteor application that houses a web application and a mobile application. The web application is built in the standard Meteor fashion (both, client, server, etc.). The mobile application is included as a package. The package.js for the mobile app only loads client-side files in the web.cordova context.
We are having issues with pushing new updates to the mobile app. The mobile app has been built using meteor, deployed via Apple Enterprise and a direct download of an Android *.apk file.
Installs go off without a hitch. When we make updates to either the app's client or the main app's server code, however, the app often crashes (white screen) or misbehaves in other ways.
Are others having issues here? Does Meteor hot code push work reliably for a built and bundled app that sits in a package? We really need to be able to push updates to our users without them having to re-download the app. We understand we could use the techniques and packages mentioned here to mitigate the disruption caused by hot code pushes, but are not able to determine whether or not this will work for a situation where we are making updates to the code intended for cordova, not the client.
Our live server also does not include the android and ios platforms due to deployment restrictions. Are those required for cordova updates to be properly pushed to connected iOS/Android apps?
