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.
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.
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'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 have an app in the App Store at version 1.1.6. I then submitted a new version/update with a version number of 1.1.7. The update was approved and now if you download the app you get all the changes that were submitted in 1.1.7 when you download the app.
However, the App Store still shows the version as 1.1.6, and when you install the app it shows as 1.1.6 on the device.
What happened to the 1.1.7 version number? I have read through the iTunes guide for new versions and I think I got everything right. Can anyone shed light on how to get the version number to update when a new version is submitted?
I have another update (1.2.0) but don't want to submit it until I understand how to get the version number to change. Thanks.
EDIT: Some additional info. Version 1.1.6 and 1.1.7 were essentially released at the same time. 1.1.6 was "Ready for Sale" but had not been released to the app store. Once 1.1.7 was approved, we released them at the same time. Not sure if that matters or not.
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.