iOS App Upload is getting CFBundleShortVersionString error message - ios

So I am trying to upload my app to the App store, and I am getting this error message.
ERROR ITMS-90060: "This bundle is invalid. The value for key CFBundleShortVersionString 'HEAD based on 1.0' in the Info.plist file must be a period-separated list of at most three non-negative integers."
If I open the log it gives me, you can clearly see the version short string is correct.
<software_assets apple_id="456805313"
bundle_short_version_string="27.1.1"
bundle_version="3221"
....
</software_assets>
What am I missing?!?

I have used pods in my project, In the info.plist of pod SVWebViewController CFBundleShortVersion was not in standard way.
You need to find non-standard CFBundleShortVersionString in info.plist file. I searched through all of them and found this in one of the repo
Before
Bundle versions string, short => Head is 0.1.2
After
Bundle versions string, short => 0.1.2
After correcting CFBundleShortVersion everything worked fine.

Check any 3rd party frameworks you've used. There are reports floating around of xcode tripping over bundle_short_version_string included in 3rd party resources pulled into the main project. For example:
CFBundleVersion must be a period separated list of at most three non-negative integers (WARNING ITMS-9000)
https://forums.developer.apple.com/thread/23581

Related

Invalid bundle structure. The binary file '***' is not permitted

This is my first time when I integrate, share extension to my app. I don't know after adding a share extension to my app I get this error while uploading my app build on Test Flight. App work fine on a device not getting any error, but when I try to upload my app a get this error.
thanks in advance
You should fix your bundle CFBundleVersion
According to Apple document as below
Each integer provides information about the build version in the format [Major].[Minor].[Patch]:
Major: A major revision number.
Minor: A minor revision number.
Patch: A maintenance release number.
You can include more integers but the system ignores them.
You can also abbreviate the build version by using only one or two integers, where missing integers in the format are interpreted as zeros. For example, 0 specifies 0.0.0, 10 specifies 10.0.0, and 10.5 specifies 10.5.0.
As well as your app bundle version you should be aware of your pods has correct short bundle versions are correct. You can check them from info.plist
removing file FAIcon from my copy bundle resource work for me.

IOS new update versioning code error meaning?

i keep on receiving this email after sometime i upload my IOS new version IPA to ITunes. But i don't know what does it mean anymore. My build version current is been increase to "0.0.27" due to upload keep on failing me. My CFBundleShortVersionString also increase to 97 due to some mistake in previous upload numbering. But i still can't seem to upload my IOS update to Itunes. Im doing phonegap cross-platform mobile application. First version is successful on 14 February 2018, and upload by appsuploader. Any clue for what i miss will be appreciated.
Invalid Version - The build with the version “0.0.15” can’t be imported because a later version has been closed for new build submissions. Choose a different version number.
Invalid or Non-Increasing CFBundleShortVersionString - The value specified in the bundle's Info.plist file for the key CFBundleShortVersionString must be a string consisting of at most three dot-separated components, where each component is composed only of the digits 0 through 9. For example, any of the following are syntactically valid values for CFBundleShortVersionString: "1.0", "4.2.1", "3.46", "1.112.0"; whereas the following are all syntactically invalid: "1.4.0.0.0.0.5", "GX5", "3.4.2b6", "2.6GM", "1.0 (Gold)", "-3.6". Additionally, each updated version of the same application must have a CFBundleShortVersionString that increases relative to that of the previous version that was actually made available for sale on the iTunes Store. For example, if a previously-available version had a CFBundleShortVersionString of "1.4", then any of the following would be acceptable as the next update: "1.4.1", "1.4.332", "1.5"; but all of the following (though syntactically valid) would be unacceptable: "1.4", "1.3", "1.3.9", "0.9". For more information about the CFBundleShortVersionString key and the Info.plist file, see Apple's Runtime Configuration Guidelines at http://developer.apple.com/library/ios/documentation/MacOSX/Conceptual/BPRuntimeConfig/index.html
Mark this as Resolve. It just an compilation conflict when selecting android and ios together. I compile the cross platform individually then can see the adobe phonegap build version is changing to latest. After that upload to ITunes and everything go smooth.

CFBundleVersion Not Matching

I'm attempting to upload an application to apple, and i keep receiving this error:
ERROR ITMS-90345: "Metadata/Info.plist Mismatch. The value for bundle_version in the metadata.xml file does not match the value for CFBundleVersion in 'App Name Here' [Payload/App Name.app]."
I can't seem to edit my CFBundleVersion in my plist so it matches, any thoughts???
You can click on your project file, then click on your target, and change in the general tab the version of your app.
What is important is that you should not have any spaces in the version, if the version that you specified in iTunesConnect is also without spaces.
I did get the same error because I had a trailing space in the version which was difficult to detect.
I just got the same problem. Looks like app store compares CFBundleVersion with the last one. The current one should be higher.
Example: current 2022.06.14 will be rejected if there is another build say 2022.07 already in the TestFlight.
If you have an app extension, make sure that the build number in the extension target is the same as in the app target.
Click on your project file(info.plist) then ensure that the MinimumOSVersion is either same as the previously submitted apps or higher. In my case, I lowered the MinimumOSVersion of my app accidentally. So after I changed it back to what it was before I was able to submit my app to Itunes Connect using application loader. You can also check for spaces in the version string if you wish and remove them.
Please check your CURRENT_PROJECT_VERSION after you change MARKETING_VERSION, or you can change CURRENT_PROJECT_VERSION to 1 (CURRENT_PROJECT_VERSION=1)

How works the Apps versioning control of the App Store?

I need to publish a new version (1.0.1.10) of an application that is published as version 1.0.1.
When trying to publish I am getting the following error:
ERROR ITMS-90060: "this bundle is invalid. The value for key CFBundleShortVersionString '1.0.1.10' in the info.plist file must be a period-separated list of at most three non-negative integers."
Can I only use three integers?
I did this procedure in the Google Play smoothly.
at most three non-negative integers
You can't use more, try something like 1.0.1100

Error ITMS-90362 -- Share Extension Xcode ios

I am trying to build an share extension, But during upload i got this error
Error ITMS -90362"Invalid info.plist value. The Value for the key
'NSExtensionActivationRule' in bundle myapp.app/Plugins/myapp.appex is
invalid
You are getting two messages I can see the problem for the second one. The Bundle Version needs to match in both targets. You have Bundle Version set to 0.0.6 in the main target and it's set to 1 in the Extension target. Change that to 0.0.6. "Build Version String, short" doesn't matter.
You'll need to show the values of the NSExtension key in the Extension target to fix the first message.

Resources