Is there a way to set the iOS build number different than the version when building with the corona simulator?

Solar2D iOS
#1

Hi Corona,

I recently submitted an app binary and it was rejected by the app review team. I made the changes they wanted and tried to upload a new build with the same version number, but the app loader gives me an error:

ERROR ITMS-9000: “Redundant Binary Upload. There already exists a binary upload with build version '1.0.2' for train '1.0.2'” 

Is there a way with corona to change the build number while keeping the version number the same? 

For example, if I enter in 1.0.2 for my version in the corona simulator popup Build for iOS, it seems to generate an app package with the build number also set to 1.0.2. But I would like to change the build number to something else such as 1.0.2.1 but still KEEP the app version at 1.0.2. That way I can submit a new binary to iTunes Connect for version 1.0.2, but have an updated build to attach to it so I can resubmit that version to the app review.

See the following thread on stack overflow: 

http://stackoverflow.com/questions/25680604/error-itms-9000-redundant-binary-upload-there-already-exists-a-binary-upload

Thanks!

#2

If you’re using a recent Daily Build, you shouldn’t have this problem. The version number in the Corona iOS Build window sets the CFShortVersionString. This is what is displayed to your users. Internally we create a unique CFBundleVersion  number based on time/date for each build. This avoids the duplicate build errors you get with iTunesConnect. You should be able to set the iOS version and keep doing builds and iTunesConnect shouldn’t complain. You can also override either version number by setting it directly in the plist section of the project’s build.settings file. The terminal output will show you the CFBundleVersion number it created when doing iOS builds. Only the Daily Builds have this feature.

#3

Thanks Tom!

I am still currently on the public build since I am just an enterprise trial user right now. I have the CFShortVersionString manually specified in my build.settings file. So it sounds like I can also manually set the CFBundleVersion to whatever I want and this should fix the issue as well.

#4

Yes, if you manually increment the CFBundleVersion string whenever you submit to iTunesConnect, that will work.

#5

Thanks I got this to work manually :slight_smile: Apple accepted the new build for the same version!

#6

If you’re using a recent Daily Build, you shouldn’t have this problem. The version number in the Corona iOS Build window sets the CFShortVersionString. This is what is displayed to your users. Internally we create a unique CFBundleVersion  number based on time/date for each build. This avoids the duplicate build errors you get with iTunesConnect. You should be able to set the iOS version and keep doing builds and iTunesConnect shouldn’t complain. You can also override either version number by setting it directly in the plist section of the project’s build.settings file. The terminal output will show you the CFBundleVersion number it created when doing iOS builds. Only the Daily Builds have this feature.

#7

Thanks Tom!

I am still currently on the public build since I am just an enterprise trial user right now. I have the CFShortVersionString manually specified in my build.settings file. So it sounds like I can also manually set the CFBundleVersion to whatever I want and this should fix the issue as well.

#8

Yes, if you manually increment the CFBundleVersion string whenever you submit to iTunesConnect, that will work.

#9

Thanks I got this to work manually :slight_smile: Apple accepted the new build for the same version!