code-pushcommands only works with a supporting Cauldron. You should have properly setup and activated a Cauldron in order to work with CodePush.
code-pushcommands. The CodePush access key is not stored in the Cauldron, for security reasons.
MyAwesomeApp, you should create an application named
MyAwesomeAppIosand another named
MyCoolAppin your Cauldron, you cannot use
MyAwesomeAppfor naming it in CodePush.
MyAwesomeAppAndroid) then you don't have to do any specific configuration in the Cauldron as this convention will be used when running
MyAwesomeAppForAndroid, you will need to specify the custom name in your Cauldron configuration. You should edit the
cauldron.jsonfile of your Cauldron manually, as we don't have commands yet to edit configuration in the Cauldron.
codePushconfig object of the native application platform, as follow:
Productionthat app center creates for you when you add your app.
MyAwesomeAppapplication, to create
Devdeployment name :
not a valid application iderror, run the
appcenter apps listcommand to get the application id to pass in for the commands.
code-pushcommands. This deployment name can be provided as a command option, however if you'd rather like to be prompted for a deployment name to choose from, you can store the deployments names associated to a native application name/platform inside the Cauldron
MyAwesomeAppAndroid in our Cauldron:
MyAwesomeAppon Android, we might use the version suffix
-qa-debugto denote a debug version built for
dev-debugto denote a
Developmentdebug version. In this case, for any given version number (for example
1.0.0) we can have three
variantsof the version :
CodePushwill only install it for versions matching the targeted version string. i.e if we are doing a CodePush release targeting
1.0.0, then, users running the
1.0.0-dev-debugversion won't get the release.
codePushconfiguration entry in your Cauldron.
-dev-debugversions are associated to your
Stagingdeployment name and
-qa-debugversions are associated to your
QAdeployment name, then you should setup the following
codePushconfiguration in your Cauldron :
codePushconfiguration in the Cauldron top level
configobject. For example, if we desired to keep track of only the last two CodePush release entries for each native application version (per deployment name), our configuration would be as follow:
react-native-code-pushdependency to your MiniApp. From your MiniApp root directory, run the following command:
codePush, as illustrated by the following sample :
installModebased on your use case.
CodePushplugin configuration. This configuration takes the
deployment keyto be used at runtime. This is at this step that you can select which deployment key to be used, based on the build type.