If you want runtime configuration (change the URLs after building), it's usually a better idea to use a separate .plist file instead of the Info.plist (since Info.plist is usually reserved for data you need to communicate to the operating system). If you need compile-time generation, you can set that up as a "Build phase" in Xcode (any Build Phase script will have access to the same macros you're injecting into your .plist).
Thanks for the tips, I'm still ramping up on ios development and the apple eco system with a deadline I barely managed. I'll take this into consideration for the next Sprint.
See "Build configuration statement" on this page:
https://developer.apple.com/library/prerelease/mac/documenta...
If you want runtime configuration (change the URLs after building), it's usually a better idea to use a separate .plist file instead of the Info.plist (since Info.plist is usually reserved for data you need to communicate to the operating system). If you need compile-time generation, you can set that up as a "Build phase" in Xcode (any Build Phase script will have access to the same macros you're injecting into your .plist).