This is what the version & build number show up as inside of xCode.
After archiving the version number appears to remain the same as the previous one.
Error message I am getting after trying to upload the application
Has anybody had this problem before or can you think of any possible fixes?
CFBundleShortVersionString CFBundleVersion Please check these two values in your info.plist file, you must have hard coded them sometime. It was the case with me. These values were hard codedly given
Related
Good day,
Just now my Xcode auto update from version 13 to 14.
After it update, I continue to build my app. I found the UI design a bit different with previous, but so far I manage to find the setting that I fill in usually.
As usual, I increase my build number from 1.1.20 to 1.1.21.
However, after I archive, I found that version is not follow what I have key in (1.1.21), it written there 1.1.2, looks like it does not get my value to do the archive.
And if I continue to Validate app or Distribute App, I will hit metadata/info.plist mismatch. the value for bundle_version in the metadata.xml file does not match the value for CFBundleVersion in...
I even restart Xcode, restart Mac still the same, even I try change my build number to 1.1.3 or some other number, the result still the same.
Even I change my project format to Xcode 13.0-compatible still the same.
1 hour ago, I was still able to build the App before the Xcode auto update. After I auto update then it hit this issue.
May I know where is my mistake?
My temporary solution is edit the info.plist to proceed first.
In the info.plist file, I change the following value to the build number I want:
<key>CFBundleVersion</key>
<string>1.1.21</string>
So as you have mentioned the Temporary, I will explain that in details.
I have also faced the same issue after upgrading from Xcode 13 to Xcode 14.
The temporary solution is to put the version name and build number directly in the info.plist as give below.
I'm getting error "Redundant Binary Upload. There already a binary upload with build version'1' for train '1.1.2" at Softwareassets" when trying upload an updated version to appStore.
However, I already incremented "build" version number. as shown below:
Moreover, I notice, one issue, even though I changed build and version numbers, but still Xcode display the old version number when display the error and also in the details under organizer windows:
Notice, actually my app version and build numbers are 1.2 and 1.2.1 respectively on General settings.
I dont know why xcode doesn't realize that version and build numbers have changed.
I am not sure that this will help, becoz even I had faced many unpredicted issues while submitting the apps recently.
But for the basics,
if app is not reviewed yet:
Your Version number must be same as It is there in itunesConnect Account,
and you can update the new build with updating only build number
And if your is reviewed or published:
you need to update both version and build numbers
Also, if possible once try to submit the build from xcode and submit the app from itunesConnect.
Hope this will help,
Thanks.
It seems I asked the wrong question. I'm getting this error because I forgot to archive the project first before uploading to Appstore.
The reason I didn't archive because archive was giving an error which I posted as as another question at stackoverflow.
When I am submitting Application through Xcode Application validation successful but when submit to Appstore Then This error Occur.
ERROR ITMS-90207: "Invalid Bundle. The bundle at 'example.app' does not contain a bundle executable
I also try Application loader Version 3.1 but same error occur.
I refer all link like
link 1
link 2
link 3
link 4
Please check your info.plist file and add below key if not
<key>CFBundleExecutable</key>
<string>$(EXECUTABLE_NAME)</string>
The connection to the info.plist file might be causing the issue. Try changing the bundle id from target and check if it reflects in the plist file and vice-versa. If this doesn't reflects copy your plist file at some other location, remove it from the app and drag and drop again, it will help. This solved my issue, hope it helps.
I was dealing with this error since yesterday and when I was about to give up I tried with a different Mac and it worked, the only difference between the OSX was that I updated to Xcode 8.2.1 and the other OSX had 8.2.
Hope it helps!
I had this issue and was banging my head on the desk for several days. I tried all solutions posted online and nothing worked. For me it ended up being corruption in my 'Bundle display name' (aka CFBundleDisplayName) key in my info plist file. There was a rogue '¿' character that would not get removed when I changed the entry in Xcode (I know this because I tried setting several keys within Xcode). I had to remove the key and re-add it get it fixed. The only way I ever saw this was to open the plist with a text editor. Xcode never rendered the bad character. If you are seeing this issue check you plist file in a text editor for any bad characters.
I had the same error during upload, I was pretty sure about the bundle structure is perfect, the executable at the correct place and the Info.plist points to the correct place, contains the correct name, just like the localized versions.
I decided to ask for help from the Apple support. After a long process it is turned out that my ~/.itmstransporter folder was corrupt or outdated.
After deleted the folder it is re-created automatically and the problem went away.
For my case, it was because i moved application loader to another disk. After moving it back to mac os disk, it works fine.
I have been trying to submit my app to the App Store, but haven't been able to get around this validation error. "Expected token not found in attributes: CFBundleShortVersionString".
I thought it was simply just including CFBundleShortVersionString in my info plist and I would be okay. However, that is not the case.
I have tried the solution here: iOS app validation error: Missing plist key CFBundleShortVersionString
But I am still getting this error.
I have cleaned my project, restarted my machine and Xcode, but now I am stuck trying to find a work around. Any help would be greatly appreciated, thank you!
Your short Bundle version string should be: 1.1
Because your build version is 1.1.2, i.e. the build 2 added.
you only have to add Bundle Short Version String in info.plist of your project
I found something to work around the problem.
I exported the .ipa file via Xcode and used Application Loader 3.0 to submit to the App Store. And it went through. The new build is now on iTunes Connect.
An update for an already existing app I have was submitted this morning. The update was very minor barely any changes were made. Apple has now sent me this email stating..
the following issues must be corrected:..
Invalid Bundle Structure - Your package contains a bundle with the following issue: IPA bundle does not include a Payload directory.
How do I fix this?
Ok, my answer has been deleted because it was not an answer to the question.
I do not have enough points to comment your question (that's what I tried to do because I obviously don't have the answer — just the same problem as you and trying to figure out why we're getting this Invalid Binary error)
As I said in my first post: I'll keep you up to date.
Today, I created a new Xcode project, with the same bundleID as the app I try to upload for a week now. It passes through the server-side pre-validation and I received a mail saying it's "Waiting for Review".
It answers one question I had since the beginning: It's not a server problem (I thought Apple had some issues with the pre-validation process).
I tried to play with architectures on this new project (for example, I only use armv7 arch for my App because of some incompatibility with third-part libraries). Still passes the server validation.
Then, I tried to copy the Info.plist file from my app to the new sample project which passes the server validation: BANG -> Invalid Binary!!
This info.plist is quite old, used since Xcode 3.0
I tried to remove some optional keys from it: still invalid binary
Then, I compared the original and needed keys with a new project's info.plist file : bang!
The "CFBundleInfoDictionaryVersion" value was empty. On a new project, the value is "6.0".
I simply set "6.0" for CFBundleInfoDictionaryVersion key and boom, it worked.
My guess is that Apple' servers are checking the info.plist file and needs a proper CFBundleInfoDictionaryVersion value in order to read the .plist file. And I think it's not happening since Xcode 5.1.1, they must have updated their server among with the release of Xcode 5.1.1, that's all.
Jeez, I can't believe how dumb it was. It's a shame that Apple does not provide a comprehensive feedback.
Hope it will work for you! Let me know!
In my Info.plist, somehow my Application requires iPhone environment was set to NO.
setting it to YES fixed this...
This worked for me
Just add the following item in your Info.plist:
LSRequiresIPhoneOS | Boolean | YES