I'm in a situation where we wanted to test 2 different versions of the App:
Version 1.0.0 is going to be released on the App Store and is currently under testing.
Version 2.0.0 is under testing only.
Let’s say I have released Version 1.0.0 - Build number 1 on Testflight.
If I wanted to release a new build for version 1.0.0 it wouldn’t be a problem… I could increase the build number and keep version number unchanged (Like Version 1.0.0 - Build 2).
Now, Let’s say that I'm also uploading Version 2.0.0 - build 3 on testflight.
Is it true that from now on I cannot upload other versions that are lower than 2.0.0?
If I've uploaded version 2.0.0 but Apple rejects my current build for 1.0.0 during the App Store review process… I couldn't send to Apple another build 1.0.0, the only way to go would be to upload a new build increasing version number to 2.0.0 or greater then?
Am I saying anything wrong?
Yes you can do any combination you want to make, like after uploading 1.0.1(2) you can upload 1.0.1(1) as well as 1.0.0(5). There is no restriction for uploading lower version or lower build.
Have a look into image and note dates.
I had uploaded v1.0.3(10000) first(13th Jul) and then uploaded v1.0.2(10200)(on 16th Jul).
Well lets make a little difference between sending the app for App Store review or Test-Flight in here:
1- You uploaded to Test-Flight 1.0.0 build 1 for testing purpose and then you need to send another one for testing purpose, which will be 1.0.0 build 2, you just keep on increasing the build number and not the version.
2- Ones you finished Testing and you want to release the build to the App Store Review lets say you sent version 1.0.0 build 2 for review, Now if apple has accepted the app and its ready for sale or pending developer release, you are forced to adjust the version number for your next release to be 1.0.1 or 1.1.0 and you can reset the build number to start from 1 again, but never version 1.0.0.
You will get an error from Xcode if you tried to upload a version that has been accepted from apple, you will need to increase the version number. always remember that.
Hope this helps u out.
Related
I uploaded a build of my app to the app store with version 4.1.10 and build number 1. I made a minor update and am wondering whether to upload it as 4.1.11 (1) or 4.1.10 (2). What difference does it make to users downloading the app?
You change app store version to indicates that this is a new version for AppStore.
You change build number to indicates that is is a new version to test before publishing to AppStore.
So, while an App version is not in AppStore, just increase the build number.
My question is when you upload a build to App Store Connect, you have Version number and build number. A Version number change triggers a App Review (this can take sometime to approve) and just a build change happens fairly immediately. So is there a guide line when to make a version change or just a build change?
The build number indicates a specific build for a specific version.
For example you can have 5 builds for version 1.0.2.
Every time you want to publish a version you need to specify which build of that version is going for approve.
When you want to submit an app update you must increase the version number, you can't submit again the same version.
If your current version is 1.0.2, build number 13, your next version can be 1.0.3, build number 1.
I'm planning to release an iOS app soon, just to speed up the AppStore Review process I want to start it earlier. I want to understand the versioning concept there.
Assume that I sent 1.0.0 to review and it's approved and ready for release (But I won't release this version).
If I send a new version, can it be still 1.0.0 or it has to be sth like 1.0.1 or 1.1.0?
Thanks
You can reject it yourself and still use the display version 1.0.0 with a different build version.
On AppStore - you can add build numbers and the version can be the same.
On Google Play - each version has to be a different version number (even when version has not released).
If version 1.0.0 is still pending review, you can reject it yourself, apply a newer 1.0.0 build and resubmit for review.
Once version 1.0.0 has been approved you would need to increase the version number, even if you never released it to the App Store, so 1.0.1, or similar would be required.
These days App Store review typically takes less than 24 hours, so you can set up all of your meta data, screenshots etc and simply upload the build and submit for review once you are happy with the code.
I am uploading my iOS app to appstore connect, I have a doubt
should I upload version 1.0? Can App Version be less than 1.0 like 0.9.0 or 0.9.1
If I use any of the above mentioned version, will apple reject my app.
Please help.
It doesn't matter. Version number visible in Appstore is the one you will set up when submitting. The first time you upload your build you can set any version number 1.0 or 0.9.0, then you should increment your version number and/or build number, otherwise itunesconnect will reject your binary.
P.S. you can find it useful: https://developer.apple.com/library/archive/technotes/tn2420/_index.html
I am about to update my app for the first time. I am in xcode and looking at the project targets. My new version number is 1.0.1 so do I just change my version number here? Do I need to increment the build number too?
The build number should really be increased by 1 every time you check in a new version into git. Build number shouldn't be 1.0.1, it should be for example 3915 (if you checked in 3915 changes into git). It's a sequential number.
If you have released 1.0.1 and want to release 1.0.2, you send the next build number and version 1.0.2 to Apple. If it is rejected, you make changes, increase the build number, and leave the version at 1.0.2. If your version is accepted, and downloaded by end users, the next time you send an upgrade to Apple it should have version 1.0.3 and again the next build number.