@danieldunderfelt Thanks for the feedback. I will see how we can improve the documentation.

When you created the staging project configuration, did you also manually create a Staging scheme?

Hi!

No, that was created when I copied the release config and made the staging config.

@danieldunderfelt Unfortunately I was unable to repro the error you were seeing.
After duplicating the release config and calling it staging + setting up the CODEPUSH_KEY config, all I did was go to Product > Scheme > Edit Scheme then set the Build Configuration to Staging. After that I ran the app and it was sync-ing against CodePush with the Staging key just fine.

What version of XCode are you on? I don't know if that matters but I'm using v7.1.1.
Also are you using CocoaPods for dependency management?

@geof90 No, not using CocoaPods. Does it manage these things for me?

When I figured out why my builds weren't working, that the third-party packages didn't have a staging config, I thought having cocoapods wouldn't matter.

@danieldunderfelt no I only asked because I wasn't using CocoaPods and I was wondering if you were.

@geof90 oh, good good!

Maybe your xcode made staging config for your third-party packages, and my xcode glitched out and didn't?

Nice, this did also fix it for me. I omitted the Step 3 (changing the project.pbxproj) and my Fabric.framework does still work fine.

However when I use different PRODUCT_NAMES for the different build environment, I am getting now a build error. I am have setup the names according to this article

When i build my release config everything works, but not when I build the debug or staging config. In these cases I get the following errors:

I have tried to fix it by

• set Target => Info => Executable file to $(PRODUCT_NAME)
• set Target => Bundler Loader to => $(BUILT_PRODUCTS_DIR)/$(PRODUCT_NAME).app/$(PRODUCT_NAME)

I have cleaned my build folder before each build.

This did not happen before, so it could be related to this issue.

(For now my workaround is to use different app icons in order to distinguish my different build environment - as outlines in the article above)

Here I solved the staging problem by correcting the TEST_HOST which is pointing to a fixed value despite the new PRODUCT_NAME.

I've changed the scheme to use the staging variation for tests builds.

I hope it helps!

Our solution might be helpful here as well: https://zeemee.engineering/how-to-set-up-multiple-schemes-configurations-in-xcode-for-your-react-native-ios-app-7da4b5237966#.pxa41apg1

really nice @huitsing! Much more complete solution!

I have the same issue, too. I use xcode 8 beta 6.
library not found for -lCodePush with build configuration "Staging".

I have fix just re-add libCodePush.a at Linked Framework and Libraries.
Now everything works fine =).

@jm555jm THX for the hint. I had quite a few external libraries and I was desperately trying to unlink and re-link them without any luck. But manually removing and re-adding them in the Link Binary with Libraries section finally solved the issue and my builds are succeeding again.

@jm555jm @flavordaaave thanks for the tip!
It took me a couple minutes to figure out exactly how to do that, so for others:

1. Select your app target
2. Make sure you are in the General Tab
3. Scroll down until Link Binary with Libraries
4. Select libCodePush
5. Press - minus button at the bottom left
6. Press + plus button and search for libCodePush
   👍

Actually after trying that I found that I was still with the Release scheme.
After changing it to staging, and after removing and re-adding the library it still doesn't work 😞
Same exact error.

+1 Same error, with the header, when on Staging Scheme :(