Here is my scenario:
We recently created a iTunes app record for our new app which is not yet available to public. So, by default iTunes shows an app(1.0) with status as 'Prepare for Submission'. (I assume we can change this default version number from v1.0 to v1.0.0 on the app record. but for clarity I am leaving it as default in my below explanation)
Now, I uploaded my first build with v1.0.0(0) to TestFlight and after 4 revisions/build uploads, I made the build v1.0.0(4) available for external testers. Now we got few bugs from the external testers and fixed them. Since we did the bug fixes, I want to change the version to v1.0.1(0) in TestFlight. Below are my questions struggling to find an answer for:
1) Since the app is not yet released and the default app record version is still v1.0, can I still upload a new version i.e. v1.0.1(0) on TestFlight ?
a) If I can do the above point(1), will it go through the beta review process again (or) will it simply process and appears on iTunes ?
b) If I can do the above point(1), lets say after 2 revisions again like when version is at v1.0.3(0), can I finally push this build to the AppStore as my first release....I mean will it override the default version v1.0 to v1.0.3 ?
2) If I cannot achieve the above point(1), then what would be the other approach?
Please suggest me how to proceed...
First, yes you can submit your new version (1.0.1) but it will still have to pass through the apple process to get approved for external test.
If I can do the above point(1), lets say after 2 revisions again like when version is at v1.0.3(0), can I finally push this build to the AppStore as my first release....I mean will it override the default version v1.0 to v1.0.3 ?
Yes, when you publish your app, you can specify the version displayed in the store so you can display v1.0!
Every time you want to make a new build available to your external tester, Apple need to approve it!
Related
I have a problem with fastlane when I publish on TestFlight a new bundle that uses the usual version (ex: 1.0.2):
Error This bundle is invalid. the value for key
CFBundleShortVersionString (1.0.2) in the Info.plist file must contain
a higher version than that of the previously approved version [1.0.2]
It seems like I need to publish a new version, but I want to publish a new build instead, keeping the same version ... how is that possible?
Edit Response:
ok, I understand ... although unlike Android, I don't see the usefulness of blocking a new build if there is the same approved version ... but thank you all!
There is no way to upload new build of the previously approved version. So in this situation you should have to create new version in iTunes Connect and then and then you can able to upload new build in Testflight.
Few cases arise:
If you want to keep same version, remove current app from app store and publish your current version.
Now there is already app with same version so you cannot allow to do this, either increase the version or go with point 1, how ever be careful with this point. You need to analyse cases, because it is already on appstore.
You can upload the same version to TestFlight with increased build number. Eg: 1.0.2(1) and 1.0.2(2) Simply increase the build version from Project settings.
I have developed app and so many times I have uploaded on iTunes connect (TestFlight). Like :
Version Build
1.5 —> 1.0 This build is live — on App Store
1.4 —> 1.9
1.4 —> 1.8
1.4 —> 1.7
1.4 —> 1.6
……….
1.3 —> 1.9
1.3 —> 1.8
……..
and so on…..
Now I need to update one change and want to give for testing to my other friends, So I am trying to upload new version `1.5 —> 1.1’ on iTunes connect (TestFlight) through Xcode, but it gives error like : Version must be higher than the existing version on iTunes connect.
Before making live, I have uploaded so many build for the same version and same via Xcode , at that time it is done successfully uploaded.
Then why it gives me error now ?
What it means to say ?
How can I upload on TestFlight for testing ?
Please suggested me, what should I do.
It could be due to your app has become Live (Ready For Sale) on the AppStore.
I think Apple consider the version life cycle completed once the version is available to public users via AppStore.
In your case, 1.5 (1) is Live on AppStore which means version 1.5 life cycle completes with final version being 1.5 (1).
So, you would not be able to add any further new build with 1.5 version. Instead, you should create a new version higher than 1.5, i.e., 1.5.1, 1.6, and then upload the builds to that newly created version.
This is just my assumption, not 100% sure.
For me.. i regularly updating build(not version) and uploading the it to testflight and works, even i have uploaded it today just 1 hour ago and it worked fine. I think, you should clean->build and do same process again. Sometimes after changing build number, you might not have build the target and directly archived, in that case, such a errors are thrown by Apple.
So the probable solution is to just
clean->build -> archieve .... do same process again and upload it to appstore.
I had the same Issue. I released 1.0 build 5 to App Store(live). Had to make some quick changes, so tried to change the build number and released to Test Flight through iTunes Connect. I got no warnings or any errors. However, when I login to iTunesConnect and check in Activity tab the build number for that specific version says "The build is invalid" with a red exclamation.
Solution: Just increase the version no, not the build no if the app is already live.
I was having problem with uploading a build of my app but I was successful uploading a build (0.0.7) of version (1.0.0) while the build (0.0.6) was still processing
But when I am trying to add internal testers to test this build, the uploaded version is not showing up instead it shows the version which is still in processing.
Does it have something to do with iTunes or I am doing something wrong?
A guy from Apple contacted me after 12 hours with this e-mail
"Thank you for providing that information. In reviewing the information and screenshots you provided, I can see that you have a build that is stuck in processing and you were able to upload subsequent builds successfully, however you are unable to test the new builds.
We’ve had some reports of this issue and it should now be resolved. In order to continue testing, you will need to submit a new build with a new version. Once you submit a new build with a new version, you will have the new builds available to select from when choosing a build to test."
So, I think uploading a new build with a new version will hopefully work
I was able to resolve the issue by logging into iTunes Connect and removing myself as an internal tester (which removed the app from my TestFlight App) and then accepting the invitation again.
Try this :
1) Launch Application Loader.
2) In the top menu bar, click Application Loader > Preferences.
3) Choose Advanced.
4) Under Transfer Protocol, deselect Aspera.
5) Close the Preferences window and proceed with the delivery.
I am also facing the same issue and i change the version of my app in Xcode and then it will be shown in the internal testing. Please just change the version of your app then it will show. Just change the version to 1.0.1 or 1.1 whatever you want. Hope this will help you.
Thanks
Regards
Mandeep Singh
This is our first iOS application on the Apple Store and v1.0 has been approved and Ready For Sales.
Now we are updating with new build v1.1 with fixes so anyone knows if current build (v1.0) is still available for testers/users while new build (v1.1) is being reviewed?
Cheers,
H
Your current version is available until you release the new version to the store for sale. You can check the "automatically release new versions" checkbox and as soon as the review passes it will release.
Yes, v1.0 is still available. There is an option to hold the build until you want it to release. Else until the new build gets updated in all apple servers, your users will still see the v1.0. Normally it takes sometime, for all the users to receive the latest version depending on their location.
I have uploaded new build(version 1.0.2) and they rejected (meta data rejection) because i didnt give test login details. After i added test login and updated then they again rejected.
Then i made some changes and uploaded a new version(version 1.0.3) itself but that version went into "Pre Release" and i tried to upload more versions like 1.0.4 etc.. but i can see every version still in pre release . Its almost 3-4 days. So just now i have uploaded one more version 1.0.6 (validation and everything was successful) now i can see 1.0.6 again come under pre release. Please help me.
If i uploaded same binary 1.0.2 then it will go to "waiting for review " state and after 5-10 minutes it showing invalid binary and rejected in red color.
Please help me... here is itunes connect screenshot:
For me, I realized my app does not support 64 bit. After Feb 1st, all new apps submitted must include 64 bit support. From looking at your upload dates, it looks like you may have come across this issue. In build settings under 'Architectures' make sure 'Standard Architectures' is set.
This is the new way of application submission apple introduced.
If you upload any new build it will go to prerelease section. Here you can add your internal testers to test this Pre-Release build..If not approved by your tester then you can add another build with same version and updated build number.This cycle can repeat..
At last if your tester approved particular build then you can go to new version in iTC and in build section if you click + button you can see all these testing build.Then you can select any of the build(probably QA approved build) to apple review.
FYI : This PreRelease is introduced after Apple acquired "TestFlight"