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
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.
Some background of the issue:
I have a Xcode project named A. It has a bundle ID com.abc.tung. It was on AppStore already and had few app version updates with no issues.
Later we decided to re-write the app and create a new project in Xcode named B. We also gave it the same bundle ID com.abc.tung. We uploaded a new build to AppStore Connect, everything was fine, it went to correct app in the AppStore Connect. Then we released it to AppStore.
The problem:
Some of the users reported an issue that even after the update to the newest version (the version that came from project B), it would still open them an old app with old functionality.
Please help me to understand how is it possible? Or even if you had similar issues, please also comment since it might also be some issues with AppStore?
Since bundle ID hasn't changed, it might be a build version question.
Need to find out what app build version was submitted to AppStore as B, and what build version was installed on the device.
The version on iOS is the release version (like 1.2.3) + a build number (can be just a single number like 4), so the full build version looks like 1.2.3(4).
It is a good idea to display the full version inside the app UI to make it easier for the end users to report it to you.
I currently have an app with version 1.0 that just got approved for the ios store.
The approval time was a little more then two weeks and during that time I fixed a major issue on my app. to test this version out on TestFlight with my testers I gave it a version 1.1 . Now I wanted to submit my 1.1 version app to the app store. In order to do that I clicked the add version but on my app and added the version 1.1. Now when I attempt to upload my project using XCODE I get the following error
Any suggestions on how I can fix this ?
If you have already posted the correct 1.1 build to TestFlight then you don't need to upload it again. You can submit it using iTunes Connect without uploading again.
If you want to submit a revised 1.1 build to the App Store, then you need to change the build number.
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.