|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
If you want to use different bundle IDs or app display names in different circumstances, update Info.plist directly. For example, create a user-defined "APP_BUNDLE_ID" build setting, and then set your target's CFBundleIdentifier to ${APP_BUNDLE_ID}, which you can then choose to define differently in your Debug vs Release build configs. You can create as many build configurations as you need to.
Once you've made CFBundleIdentifier or CFBundleDisplayName dependent on your build configuration, you could even override them at runtime as arguments to xcodebuild, but to do so would be foolish. It's pathological to put your build server in charge of determining essential metadata like your bundle ID or displayed bundle name, because it means the project can't build correctly anywhere else.
In my opinion, this feature request should be closed without action.