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.
Related
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 accidentally submitted an app with a version number that is way over the existing version to TestFlight. i.e existing version is 1.1.1(5) and mistakenly I submitted 3.1.1(1.) Now when I try to submit an app to TestFlight with previous version with a build number slightly over than the previous (i.e 1.1.1(6)) I am not permitted. Is it possible to revert/delete the app with accidental build version.
You can try to reset your version via website #madu
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.
I mean: if beta say v2.2.4 build 1234 proves to be good, and will make its way to the App Store (this means the final release version will be the same (v2.2.4 build 1234). Will beta testers be able to "update" to the App Store version (which has the same version/build no.) to avoid their app become unusable after 30 days (when testflight beta validity ends)?
Or, is it even wise to use the same version/build number used in the last successful beta on the production version?
Short Answer: YES
It's perfectly fine to use the same beta build for production version. We do that all the time. Version number won't be an issue, in fact it is recommended.
The users will be able to download/update to App store version by downloading from App Store and can even go back to the beta build by again downloading it from Testflight.
I had uploaded an app on app store with version 1.1.0.
It was accepted and is now on sale.
Now I have made small fixes and need to submit the app again.
Will I be able to submit the app on store, if I keep the same version.
Build version is not the version that app-store uses. It's just for the purpose of developers to refer for themselves. Both values needs to be incremented for application to upload.
Bundle version is the important one and should be updated if you want to update your app in app-store. It will also be shown in app-store.
It is necessary to change the version of the app before uploading to app store. First you need to create a new app with new version like 1.1.1 And the same version you have to update in your info.plist file in version field OR you can change it in the Summary section 1.1.1
Build Version - This is for the developers to track of the build
App-version - this is for the application version check - using which the user's get a notification about a new version of the application being available for download.
Ideally, I don't think there is any reason to upload a fresh build without changing the app-version. The latest updates to iTunes connect enforces incremented Build version.