Skip to content
This repository was archived by the owner on May 20, 2025. It is now read-only.

Commit 57626cf

Browse files
committed
Adding deployment key detail to Java sample
1 parent e2c967f commit 57626cf

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

README.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ NSURL *jsCodeLocation;
125125

126126
To let the CodePush runtime know which deployment it should query for updates against, perform the following steps:
127127

128-
1. Open your app's `Info.plist` file and add a new entry named `CodePushDeploymentKey`, whose value is the key of the deployment you want to configure this app against (e.g. the key for the `Staging` deployment for the `FooBar` app). You can retrieve this value by running `code-push deployment ls <appName> -k` in the CodePush CLI, and copying the value of the `Deployment Key` column which corresponds to the deployment you want to use (see below). Note that using the deployment's name (e.g. Staging) will not work. That "friendly name" is intended only for authenticated management usage from the CLI, and not for public consumption within your app.
128+
1. Open your app's `Info.plist` file and add a new entry named `CodePushDeploymentKey`, whose value is the key of the deployment you want to configure this app against (e.g. the key for the `Staging` deployment for the `FooBar` app). You can retrieve this value by running `code-push deployment ls <appName> -k` in the CodePush CLI (the `-k` flag is necessary since keys aren't displayed by default) and copying the value of the `Deployment Key` column which corresponds to the deployment you want to use (see below). Note that using the deployment's name (e.g. Staging) will not work. That "friendly name" is intended only for authenticated management usage from the CLI, and not for public consumption within your app.
129129

130130
![Deployment list](https://cloud.githubusercontent.com/assets/116461/11601733/13011d5e-9a8a-11e5-9ce2-b100498ffb34.png)
131131

@@ -176,7 +176,8 @@ After installing the plugin and syncing your Android Studio project with Gradle,
176176
@Override
177177
protected void onCreate(Bundle savedInstanceState) {
178178
...
179-
// 3. Initialize CodePush with your deployment key and an instance of your MainActivity.
179+
// 3. Initialize CodePush with your deployment key and an instance of your MainActivity. If you don't
180+
// already have it, you can run "code-push deployment ls <appName> -k" in order to retrieve your key.
180181
CodePush codePush = new CodePush("d73bf5d8-4fbd-4e55-a837-accd328a21ba", this, BuildConfig.DEBUG);
181182
...
182183
mReactInstanceManager = ReactInstanceManager.builder()
@@ -239,7 +240,8 @@ After installing the plugin and syncing your Android Studio project with Gradle,
239240
240241
@Override
241242
protected List<ReactPackage> getPackages() {
242-
// 4. Instantiate an instance of the CodePush runtime, using the right deployment key
243+
// 4. Instantiate an instance of the CodePush runtime, using the right deployment key. If you don't
244+
// already have it, you can run "code-push deployment ls <appName> -k" to retrieve your key.
243245
this._codePush = new CodePush("0dsIDongIcoH0mqAmoR0CYb5FhBZNy1w4Bf-l", this, BuildConfig.DEBUG);
244246
245247
// 5. Add the CodePush package to the list of existing packages

0 commit comments

Comments
 (0)