From 9f4eef363d7d422096b9d6baf2f1a9f735c848da Mon Sep 17 00:00:00 2001 From: Jodi Warren Date: Mon, 8 Jan 2018 06:30:10 +0000 Subject: [PATCH] Add tip for CocoaPod users with new release config (#1130) --- docs/multi-deployment-testing-ios.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/multi-deployment-testing-ios.md b/docs/multi-deployment-testing-ios.md index c13818b..a226f84 100644 --- a/docs/multi-deployment-testing-ios.md +++ b/docs/multi-deployment-testing-ios.md @@ -46,6 +46,8 @@ To set this up, perform the following steps: And that's it! Now when you run or build your app, your staging builds will automatically be configured to sync with your `Staging` deployment, and your release builds will be configured to sync with your `Production` deployment. +*NOTE: CocoaPods users may need to run `pod install` before building with their new release configuration.* + *Note: If you encounter the error message `ld: library not found for ...`, please consult [this issue](https://github.com/Microsoft/react-native-code-push/issues/426) for a possible solution.* -Additionally, if you want to give them seperate names and/or icons, you can modify the `Product Bundle Identifier`, `Product Name` and `Asset Catalog App Icon Set Name` build settings, which will allow your staging builds to be distinguishable from release builds when installed on the same device. \ No newline at end of file +Additionally, if you want to give them seperate names and/or icons, you can modify the `Product Bundle Identifier`, `Product Name` and `Asset Catalog App Icon Set Name` build settings, which will allow your staging builds to be distinguishable from release builds when installed on the same device.