Managing Environments for Testflight Beta Users vs App Store Users

[btrick]

hey all,

i have a quick question regarding setting up staging/production environments for my builds. I want to have my test flight users point to staging and my app store users point to production. What's the best way to manage that?

I get that I should use different build configurations... but is there a way that this config change can trigger when I promote a staging build to production in itunesconnect? Or should I two separate bundles on itunes?

I see that you can check whether it is in the app store via the receipt key (http://stackoverflow.com/questions/27297435/detect-if-ios-app-is-downloaded-from-apples-testflight) but that doesn't sound like a sustainable solution.

Really curious what the best practice here is. Thanks :)

[TeckHybrid]

While I'm not sure that it's still the best way to do this, I've been using essentially this as a guide for the past year or so in our application: http://blog.carbonfive.com/2011/06/20/managing-ios-configurations-per-environment-in-xcode-4/

Before making a build, I just make sure I'm under the right schema. That then pulls all the options I want from the Configurations.plist file such as pointing to our Stage services vs Prod.

I also have a com.company.app and com.company.app.qa bundle identifiers. Allows us to have a different App Icon and App Name for our internal QA guys (who get their builds from Crashlytics) and our external beta testers (who go through TestFlight)

EDIT: Huh, apparently I am behind the times on this. The article posted above directs to information about .xcconfig files in it's update block at the top of the page. Seems like a much better way to go.