As iTunesConnect has introduced the new feature to expire the build which eventually remove the build from iTunesConnect. After doing that i wanted to upload the new build with same App version and Build version but getting below error
ERROR ITMS-4238: "Redundant Binary Upload. There already exists a binary upload with build version '1.2.8' for train '1.2.0'" at SoftwareAssets/PreReleaseSoftwareAsset
Is it possible with new iTunesConnect?
This is not possible. Suppose you already have version number 1.0 in App Store then new version must be greater than 1.0.
Refer following link for more details: https://developer.apple.com/library/content/technotes/tn2420/_index.html
Version number and build number checklist
Here are some things you can check when submitting a new build to the App Store. Making sure you have your version number and build number set properly will help you by avoiding having your app automatically rejected for having them improperly configured.
For each new version of your app, you need to invent a new version number. This number should be a greater value than the last Version Number that you used. Though you may provide many builds for any particular release of your App, you only need to use one new Version Number for each new release of your App.
You cannot re-use version numbers.
You cannot re-use version numbers.
For every new build you submit, you will need to invent a new build number whose value is greater than the last build number you used (for that same version). For iOS apps, you may re-use build numbers when submitting different versions. For macOS apps, you must chose a new build number for every submission that is unique and has never been used before in any submission you have provided to the App Store (including build numbers used in previous versions of your app).
For iOS apps you can re-use build numbers in different release trains, but you cannot re-use build numbers within the same release train. For macOS apps, you cannot re-use build numbers in any release train.
Related
This is the first time I am trying to build and release a mobile app (Android). I have used Flutter for developing the app.
After developing the app I have successfully released (internal-test-release) the app to Google Play Console. There were so many modifications carried into the app after releasing so I have to do multiple releases(internal-test-release), for each release I incremented the version value in pubspec.yml. Now the version value reached 2.0.4+9 from 1.0.0+1.
Where 2.0.4 is the version number and 9 is the build number as per Flutter documentation
Every time I upload a release I am not able to see an update option in the play store, I have to delete the app from the device and install it again. (Expected to do an update of the existing app)
I think the issue is with how I do the increment of the version number and build number in each release. So, how to change the version number and build number while updating an app in the Google play console, so that the installed app will show an update button in the play store.
This is how my current pubspec.yml version section looks like:
ref-link
You can change the version number and build in your pubspec.yamal
Example version: 1.0.0+1 to version: 1.0.0+2
Step 1:
Create a new release (in my case open testing the process should be the same for release mode also)
Step 2:
Enter details and upload APP bundle
App bundel
Step 3:
Save => Review Release => Start roll out
Step 4: Wait till the review process is complete
Your app's update is uploaded and pending review.
Step 5
After the review is done your users will update to the latest version of your app gradually. The update may take some time to reflect in the google play store.
Note:
1)In the above example version number is the same but the build number is different so it is treated as an update in the google play store. But it is highly recommended to change the version number also.
2)The example images provided are from open testing (beta) the process should be the same for the release version also.
I already have an app published on the app store but I have made changes and want to submit a newer version. How do I do this? Do I have to make a complete new app version and enter every detail again?
What about the data inside the app will people who used my app lose all the data on the app?
Hi and welcome to stackoverflow. To update an iOS app, you will need to re-use the exact same bundle ID as the previous version and increment / increase the version number. Same applies to subsequent builds submitted to App Store Connect.
1) In Xcode make sure to use the exact same bundle identifier (You can look it up on https://appstoreconnect.apple.com if you can't remember it)
2) Then set the Version to the new version. This does not need to be the exact same as on App Store Connect (which is the customer facing number), but I can only highly recommend using the same to not get confused.
2A) If you already have a build uploaded for the new version, you need to increment the build version as well. (i.e. if you have build 1.0.0, next one can be 1.0.1)
3) Create a new version of your app on App Store Connect. This can be done independently from your work in Xcode and you can even upload a new build even though there is no new version yet.
Any changes inside your build requires a new update for you app.
How do I do this?
First you have to add a new version in AppStore Connect. The only thing which is required is the text for the update i think, the rest is optional(Screenshots etc.).
After that you can upload a new version from Xcode (or Application Loader).
- increase the build number of your build target
- archive your app and upload it to AppStore Connect.
After a while your build is available in AppStore Connect and you can add it to your new version and send it to review.
What about the data inside the app will people who used my app lose all the data on the app?
Files in the documents directory will not be deleted if a user updates your app
Data in the UserDefaults will also not deleted
Files in the cache directory can be deleted every time
I uploaded the app in App Store, and now it in "Pending Developer Release" status. But I want give it to testers before release. I have no troubles with internal testers, I gave them access to application without problems. But I have trouble with external testers with the same binary. There is an error:
CFBundleShortVersionString in info.plist must be higher than 1.0
What should I do, if I don't want to reload binary, because I can lose the "Pending Developer Release" status?
When you release a new version using Apple's distribution system (i.e. App Store or TestFlight) the version number needs to be higher than the previous release.
If the app is still in testing, it shouldn't have even reached 1.0 yet. Start with 0.1 and increment up to 0.999 as development milestones are reached. Once it's tested and ready for release, make it 1.0. This is my thinking on the issue anyway; the actual value is not important, however some users may query why a newly-released app has a version number of 1.452, for example.
Note that the number is not a floating point; instead it's major.minor and major does not increment when minor goes above 9; instead the version becomes 1.10 until you rework it sufficiently that the major becomes 2 and the minor resets to 0, and so on.
So to answer your question, change CFBundleShortVersionString to 1.1.
As for CFBundleVersion, that should be an integer that increments from 1 whenever a build is performed and source files have changed (again, in my opinion), which can be managed with a script as posted in this answer.
I have client with an app in the app store that was at version 4.05 and they accidentally submitted a new build as version 5.06 when they meant to submit it as 4.06. They aren't ready yet for a full version number increase. Long story.
Is it possible to submit the next version as 4.06 to get it back on track? Or is not allowed to upload a lower version to iTunes Connect?
Yes. The version numbers only need be distinct.
From the Developer Guide:
A Version Number The unique version
number of the app. Keep the following
in mind:
Use typical software versioning conventions (for example, “1.0 or
1.0.1 or
1.1”).
Do not include words such as “build” , “version” or “beta” in your version
number. This will appear next to your
application icon on the app product
page.
Perviously the client uploaded same app on iTunes connect and rejected for some reason.
After some modifications I need to upload the binary again.
The previous binary details are,
Now, here are the current info.plist details,
I am using Xcode 4.0
When I tried to validate product from Xcode I got this error,
I tried different different CFBundleVersion in the Info.plist. but still error occurs.
I cleaned project, deleted build, also re-installed Xcode and retried but no use.
Please help me.
So it looks like this needs to be an ever-increasing version number and can't reset when the marketing version number changes. It seems like you could use your VCS revision number here; in my app I display the marketing version number and if the user "clicks" on it it adds the build number (CFBundleVersion) on the end. The primary purpose of this is to keep the version number clean and simple, but also allow QA and beta testers to determine the exact version of the product they're testing. The Subversion revision number would certainly help us track down the build being used, but in this case that'll be a strange version number jump for me (6 -> ~74000).
basically i had to change 1.1f to 1.11 in both itunes connect and in xcode. the f had to be removed from the version number. no alphas allowed !
Reference: Can't Update App with New Version Number