Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iOS Cannot update app: CFBundleVersion in info.plist is wrong

N

Nobita

macrumors 6502
Original poster
Oct 5, 2008
425
2
La la land
Hi all,

I'm trying to push an update for my app, what I did was:

- duplicate the project folder, because I want to keep a copy of 1.0
- fix the bugs and add new features
- change the Bundle Version key to 1.1 (later I also changed Bundle Version string, short key).

However it doesn't seem to be working. Error message from itunesconnect says:

The binary you uploaded was invalid. The key CFBundleVersion in the Info.plist file must contain a higher version than that of the previously uploaded version.
Click to expand...

Is there anything wrong that I've done? I've even tried changing the bundle version to 1.2, 1.3, 1.10, 1.19, 2.0, 3.0, etc and it still doesn't work (I've spent almost 3 hours doing this and googling and cleaning, rebuild, etc).
 
Nobita said:
- duplicate the project folder, because I want to keep a copy of 1.0
Click to expand...

Good God, man! Use an SCM!

Nobita said:
Is there anything wrong that I've done?
Click to expand...

You have to put a version number into the iTunes Connect form, as well as CFBundleVersion, when submitting the application. Are you 100% sure your original submission specified "1.0"?
 
Can you tell me how to do it in Xcode?

I'm sure I've put down 1.0 in my original submission. I've double checked! What else could be wrong?
 
Rightclick your target in the left hand pane and select "clean"

Rebuild, rezip and resubmit to the app store.

EDIT: oh you say you have cleaned.

Ok, in your info.plist file you have a key named "Bundle version" right? What was it on your old build, and what is it in your new one?
 
Wait, there's one more thing that I should mention before contacting Apple developer support:

I built my app using iPhone SDK 4, BUT I specified the iPhone version to be 3.0. In this case, do I have to actually download iPhone SDK 3.2 and rebuilt using that?
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_0 like Mac OS X; en-us) AppleWebKit/532.9 (KHTML, like Gecko) Version/4.0.4 Mobile/8A260b Safari/531.21.10)

If beta 3 behaves like beta 2, then yes. Apple wouldn't accept apps built with it, no matter what targe version you selected. You should have 3.2 and 4.0 both installed. Their docs even say so.
 
Nobita said:
I built my app using iPhone SDK 4...
Click to expand...

Read the beta SDK documentation. You can't submit apps built with the tools that came with the beta SDK. Uninstall and install the production SDK.

If the problem still exists, you might also try doing a careful compare (hex dump) and examination of the version strings in the old and new plist files.
 
Ahh, thank you guys, I'm such a dumbhead... I wonder why Apple don't just enable the beta sdk to include the regular one by default. Will try again soon.
 
dejo said:
Because it's beta, so there might be issues. They want apps submitted against the latest release SDK because that is a known (or much more known) quantity.
Click to expand...

Okay, fair enough... Is there any way to have both beta Xcode and the stable release on the same computer?

I would thought that the beta part of the beta sdk release is the 4.0 sdk only (the 3.0-3.2 that's included in the sdk is not beta).
 
Okay, so apparently it's now working for me.. I really wonder what happened before. I did not change any of my submitting methods.
 
I've had exactly the same issue for the first time today and after submitting a fair number of apps.

My original app was version 1.0.6
I went to submit the update as 1.0.7 and it gave this error.
I rebuilt with 1.1.0 in plist (after full clean, even deleting the build directory) and apploader rejected it again with same error.

I finally tried 2.0.0 in desperation and that worked fine. My guess is that the plist info is cached somewhere and after a while it obliterates it. The only alternatives I can think of is the apploader struggles with x.y.z version numbers or reading the old version number correctly... both seem fairly unlikely.

I really can't see the second being realistic as I expect many people use the x.y.z format but who knows... certainly some magic happening and my money is on it picking up old data somewhere. (I should mention that if you show contents of the built .app file you can see the info.plist file there to see if it has indeed got the latest version number. My 2.0.0 worked a charm when I discovered I could open this up).
 
I'm having the same issue as well, trying to go from 1.01 to 1.1. I double checked everything and can't see what I've done wrong; there's definitely no mistake in what was entered in iTunes Connect nor in the CFBundleIdentifier value for either the previously submitted 1.01 version or the new 1.1 version.
 
OK I just found out what I was doing wrong: 1.01 is considered to be the same as 1.1, so I had to go up to 1.2.
 
same deal..

I too just experienced the same thing.

My App version was 1.1 and I tried to make a 1.2 -- no luck.

Tried 2.0 - also no luck.

Then tried 2.0.1 and it worked.

Only change that I can think of from 1.1 to the recent build is that this one uses the newer Xcode and 4.0 SDK (although I'm only compiling to a 3.0 build).

There's something wrong with Apple's check on this number -- this isn't the first time this has happened. Not sure where/how to file a bug report to Apple on this but it seems like a lot of people have experienced it -- I wonder what the triggers are.

-Eric
 
Decimal points?

I'll hazard a guess that once you've gone two decimal points, you can't go back. Version 6.7 would not validate but 6.70 did.

Dan
 
My previous version was 6.51 and I'm guessing that Apple does not sort with the decimal point. Thus 51 is larger than 7.

In your case: 1.1.0 is larger than 1.0.9.

Dan
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back