I received the following email from Apple when I submit an app update:
We have discovered one or more issues with your recent delivery for
"Project". Your delivery was successful, but you may
wish to correct the following issues in your next delivery:CFBundleVersion Mismatch – The CFBundleVersion value '1' of extension
'Project.app/PlugIns/ProjectTodayExtension.appex' does not
match the CFBundleVersion value '985' of its containing iOS
application 'Project.app'.CFBundleShortVersionString Mismatch – The CFBundleShortVersionString
value '1.0' of extension 'Project.app/PlugIns/ProjectTodayExtension.appex' does not
match the CFBundleShortVersionString value '2.1.6' of its containing
iOS application 'Project.app'.After you’ve corrected the issues, you can use Xcode or Application
Loader to upload a new binary to iTunes Connect.
Is there any way of use the same CFBundleVersion and CFBundleShortVersionString in all targets to prevent this?
Best Solution
My solution is:
For CFBundleShortVersionString:
CFBundleVersion: you could do the same for CFBundleVersion, but somehow I wanted this value to be computed from my GIT repo commit count. I´ve done it like this: