You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 20, 2025. It is now read-only.
The `release-react` command enables such a simple workflow because it provides many sensible defaults (e.g. generarting a release bundle, assuming your app's entry file on iOS is either `index.ios.js`or`index.js`). However, all of these defaults can be customized to allow incremental flexibility as neccessary, which makes it a good fit for most scenarios.
316
+
The `release-react` command enables such a simple workflow because it provides many sensible defaults (e.g. generating a release bundle, assuming your app's entry file on iOS is either `index.ios.js`or`index.js`). However, all of these defaults can be customized to allow incremental flexibility as neccessary, which makes it a good fit for most scenarios.
317
317
318
318
```shell
319
319
# Release a mandatory update with a changelog
320
-
code-push release-react MyApp ios -m -description "Modified the header color"
320
+
code-push release-react MyApp ios -m --description "Modified the header color"
321
321
322
322
# Release an update for an app that uses a non-standard entry file name, and also capture
323
323
# the sourcemap file generated by react-native bundle
@@ -741,4 +741,4 @@ Now you'll be able to see CodePush logs in either debug or release mode, on both
741
741
| Update not being discovered | Double-check that the version of your running app (e.g. `1.0.0`) matches the version you specified when releasing the update to CodePush. Additionally, make sure that you are releasing to the same deployment that your app is configured to sync with. |
742
742
| Update not being displayed after restart | If you're not calling `sync` on app start (e.g. within `componentDidMount` of your root component), then you need to explicitly call `notifyApplicationReady` on app start, otherwise, the plugin will think your update failed and roll it back. |
743
743
|Images dissappear after installing CodePush update |If your app is using the ReactNative assets system to load images (i.e. the `require(./foo.png)` syntax), then you **MUST** release your assets along with your JS bundle to CodePush. Follow [these instructions](#releasing-updates-javascript--images) to see how to do this. |
744
-
|NoJS bundle is being found when running your app against the iOS simulator |By default, ReactNative doesn't generate your JS bundle when running against the simulator. Therefore, if you're using`[CodePush bundleURL]`, and targetting the iOS simulator, you may be getting a `nil` result. This issue will be fixed inRN0.22.0, but only for release builds. You can unblock this scenario right now by making [this change](https://github.com/facebook/react-native/commit/9ae3714f4bebdd2bcab4d7fdbf23acebdc5ed2ba) locally.
744
+
|NoJS bundle is being found when running your app against the iOS simulator |By default, ReactNative doesn't generate your JS bundle when running against the simulator. Therefore, if you're using`[CodePush bundleURL]`, and targetting the iOS simulator, you may be getting a `nil` result. This issue will be fixed inRN0.22.0, but only for release builds. You can unblock this scenario right now by making [this change](https://github.com/facebook/react-native/commit/9ae3714f4bebdd2bcab4d7fdbf23acebdc5ed2ba) locally.
0 commit comments