Info.plist has no CFBundleVersion, or its value is not a string
The bundle's Info.plist does not contain a CFBundleVersion key or its value is not a stringShort answer
CFBundleVersion is the build number and must be a string of one to three integers separated by periods, such as 12 or 1.4.2. The error means the key is absent in the built Info.plist, or its value is empty or has other characters. Check the built file, then fix the plist or the build setting.
Fix it fast
1Find out which cause you have
Read the Info.plist that was actually built, not the one in the source tree. The two can differ, because Xcode merges build settings into it.
plutil -p path/to/Build/Products/Debug-iphoneos/MyApp.app/Info.plist | grep -i bundle2Match what you see, then jump to its fix
- 1
The project has no Info.plist file; the built plist has no CFBundleVersion lineXcode generates the Info.plist, and the build number setting is emptyFix - 2
The Info.plist file in the project has CFBundleVersion as a number, or no such key at allA hand-written Info.plist lacks the key or has the wrong typeFix - 3
CFBundleVersion exists but looks like 2.0-beta or build 5The value has letters or a suffix such as -betaFix
- 1
What does the error look like?
The bundle's Info.plist does not contain a CFBundleVersion key or its value is not a string
Cause 1 of 3
Xcode generates the Info.plist, and the build number setting is empty
1Check
When Generate Info.plist File is on, Xcode takes CFBundleVersion from the build setting CURRENT_PROJECT_VERSION. If that setting is empty, the key has nothing to carry.
xcodebuild -project MyApp.xcodeproj -target MyApp -showBuildSettings | grep -E "GENERATE_INFOPLIST_FILE|CURRENT_PROJECT_VERSION"2Fix
Set a Current Project Version for the target in Build Settings (Versioning), as an integer or a number with a decimal point. The value 1 is fine for a first build.
CURRENT_PROJECT_VERSION = 13Verify
Rebuild and read the built plist again; CFBundleVersion is now present.
plutil -p path/to/MyApp.app/Info.plist | grep CFBundleVersionConfirmed by developer.apple.com
Cause 2 of 3
A hand-written Info.plist lacks the key or has the wrong type
1Check
The key must be a string. Apple describes it as machine-readable, made of one to three integers separated by periods. A value typed as Number in the plist editor is not a string.
plutil -p MyApp/Info.plist | grep -i CFBundleVersion2Fix
Add or correct the key so it is a string, using the build setting so the number lives in one place.
<key>CFBundleVersion</key>
<string>$(CURRENT_PROJECT_VERSION)</string>3Verify
The built plist shows the number from the build setting.
plutil -p path/to/MyApp.app/Info.plist | grep CFBundleVersionConfirmed by developer.apple.com
Cause 3 of 3
The value has letters or a suffix such as -beta
1Check
Apple says the string can only contain the digits 0 to 9 and periods. Anything else, including letters, breaks the format.
xcodebuild -project MyApp.xcodeproj -target MyApp -showBuildSettings | grep CURRENT_PROJECT_VERSION2Fix
Keep only digits and periods in the build number. Put names such as beta in the marketing version label or your branch name instead.
CURRENT_PROJECT_VERSION = 423Verify
Rebuild; the error is gone and the built plist shows the plain number.
plutil -p path/to/MyApp.app/Info.plist | grep CFBundleVersionConfirmed by developer.apple.com
How do I stop it coming back?
- Keep the build number only in CURRENT_PROJECT_VERSION and reference it from the plist.
- Let your CI step set CURRENT_PROJECT_VERSION to a plain integer.
- Check the built Info.plist, not the source one, when a version key looks missing.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Related fixes
Mobile apps
Cannot change the App Privacy answers in App Store Connect
Publish Your App Privacy Responses?
Only the Account Holder, Admin and App Manager roles can answer the App Privacy questions.
2 causes, each with a fixMobile apps
App record creation fails because you lack permission
You cannot add a new app in App Store Connect as a Developer or limited user
Only the Account Holder, an Admin or an App Manager can create an app record, and Apple blocks it until the Account Holder has signed the latest agreement.
3 causes, each with a fixMobile apps
You cannot find the button to pull your app back from review
No 'remove this version from review' message appears on the version page
There is no button called Reject Binary.
3 causes, each with a fixMobile apps
Your Apple Account cannot sign in to App Store Connect
Sign-in to App Store Connect is refused for an account that should have access
App Store Connect does not open to every Apple Account.
3 causes, each with a fixMobile apps
Apple rejected the app under Guideline 4.3, Design: Spam
Guideline 4.3(b) - Design - Spam
Guideline 4.3 is Apple's duplicate rule.
5 causes, each with a fixMobile apps
App Store Connect rejects a screenshot because it has transparency
Images can't include alpha channels or transparencies.
App Store Connect does not accept screenshots that carry an alpha channel or transparent pixels.
2 causes, each with a fix