I had read once that if in iTunes Connect you marked a binary as "hold for developer release", there was a way to install that version from the app store instead of the current version in the store - thus allowing for one final check that the binary was good before release, and to ensure which binary was actually submitted.
I was unable to find a way to link to the approved binary though in a recent submission. Does anyone know how you can install an app store binary that has been approved before you release it?
What I do is an archive build (a release build). Then in the Organizer I choose the archive and then distribute it as an ad-hoc build. The resulting ipa file gets installed into iTunes then that version gets synced to an iOS device for testing. If it all looks good I then go back to the Organizer and choose the same archive. This time I choose to do an App Store distribution and submit the app to Apple for review.
The only difference between what you end up testing and what ends up in the App Store is how the app is signed. It's the same binary otherwise.
I think I may have found the answer in the response to this question:
Submitting third version of an iOS app via iTunesConnect before app goes live
Basically the idea is you could set a future release date, and click the release button - the binary would not go out until that date, and theoretically then there would be some way in iTunes Connect to find a link to use to install the approved binary from Apple.
That is all hypothetical, the next time I have an application ready for release I will attempt that and adjust this answer (unless someone else provides a clear answer before me).
Related
I am trying to upload an app to the app store. I have uploaded the app to apple connect but am unable to choose the build.
I did a little research and found that you are supposed to press a plus sign next to the build to choose the correct build, but there is no plus sign.
How should I choose my build?
I have seen this before when I’ve submitted builds to AppStore connect. Make sure the version number matches that of the version you are showing on your apps release/description. If this does not match you won’t be able to attach that build to that version because the App Store does not think it belongs.
You can check the “version history” tab in your App Store setup to see what the status of that version build is. When it’s done processing you will be able to add the build as long as that version matches what your preparing.
When you upload a build to app store it generally takes around 10-15 mins to process the build. You can check for the same in the Testflight tab of the itunesConnect.
Once it is processed then and then only it will be available for selecting with a plus button.
So, either way, you need to choose the build.
Possible ways you can upload build to AppStore
Using XCode
Using Transporter
Reasons the build maybe not available in AppStore after upload
Your build has some issues, in this case you will get an email notification as build rejection
If you are uploading some build with different versions.
One of my iOS app is in "Pending Developer Release" state in App Store Connect. Its been a long time (around 3 months) it got approved. Now this ipa file is removed from testFlight. can anyone let me know please the way to get access of this ipa file in App Store Connect? I need to check something in app before "Release this version".
Thanks in advance!
that is currently not supported. You could only submit a new build, which would be available in TestFLight for the next 90 days.
It was never possible to download the IPA file you uploaded to App Store Connect from Apple. Make sure to store your source code and possibly IPA files in source control (e.g. GitHub, Bitbucket or similar).
As already stated TestFlight builds are available for testing for a 90 days period, but this has nothing to do with how long Apple "stores" the build. In fact you can select any uploaded build for a version and submit it for review. The TestFlight time limit is just for security purpose, so that there is no alternative way to distribute apps.
One of my app is uploaded on mobile store, then after some months I have add new build but did not submit that build for review.
Now I updated my app with new designs and lots of changes. and I wanted to upload this new version on store. But I don’t know how to add app.
Because when I click on iTunes Connect --> My Apps --> App Store --> + VERSION OR PLATFORM, it shows only tvOS and iOS is disabled.
So now, how can I remove app from Waiting for Upload and how can I add new build ?
Here is screen shot :
I have read all documents provided by Apple Inc., but I didn’t found any option….related my scenario.
https://developer.apple.com/library/content/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/ReplacingYourAppWithANewVersion.html
https://developer.apple.com/library/content/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/ChangingAppStatus.html#//apple_ref/doc/uid/TP40011225-CH30-SW34
https://developer.apple.com/library/content/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/UploadingBinariesforanApp.html
https://developer.apple.com/library/content/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/SubmittingTheApp.html
If anyone knows, please let me know.
Thanks.
One more thing I forgot to tell that Also I want to update screenshots and description details.
For creating a brand new version, just upload the binary, and then cancel it. As I see you updated your question, this is a final solution for you then.
For uploading a build:
1. Access the version page.
Sou you should see a frame that will contain your build.
2. Your binary should be uploaded via
a) Xcode
b) Application loader
iTunes connect will pair your binary with the version according to the App ID and version saved in the Xcode target settings.
If you need to have the version of 2.0 for instance, change the version number both in
Xcode target build settings
within the App version page
First Try to upload it again.
If your upload is successful, it should be changed your status to Waiting For Review.
after change the status to waiting for uplaod -->> waiting for review and after that you an remove this app an add the new version and uplaod again.
follow this step:
step1- you can upload this build and change the status to waiting for review.
step2- after change the status you can delete this version.
step3- and create the new version and upload again with same screen shots.
To delete an app from the store and iTunes Connect
Open the App Details page for the app, as described in Creating an iTunes Connect Record for an App.
Make sure that the app status allows deletion.
You can delete your app if there is at least one approved version of the app and the latest version status is one of the following:
Prepare for Submission
Invalid Binary
Developer Rejected
Rejected
Metadata Rejected
Developer Removed From Sale
Removed from Sale
If your app has a different status, you can delete the app by first rejecting the build or by removing the app from sale. See Viewing and Changing Your App’s Status and Availability.
You can see more details at Transferring And Deleting Apps
Status for your Version 1.4 is waiting for upload. That means you must upload the App with Version 1.4 If you have already uploaded the app with version 1.4 and you don't want to use that build just increase the build number and keep the version number same 1.4.
Image with Build Number
I have an app in app store and I did few bug fixes. Then I uploaded it to the app store and released the build. But after I installed the app, that fixes I did, didn't apply on the build. It is same as the old one. I uploaded the build through Application Loader. Why is this happening? Please help.
Are you sure you correctly incremented your app's version, archived your app with fixes, uploaded to iTunes Connect, submitted for review, heard back from Apple with an approval, and distributed to the App Store? If you did all that, things really should work.
Firstly, set up a script to increment the build number every time you run (or archive) your project in Xcode. Instructions here.
Secondly, add a label somewhere in your app's user interface and populate it with the build number.
self.buildNumberLabel.text = [[NSBundle mainBundle] objectForInfoDictionaryKey:#"CFBundleVersion"];
Now you will be able to confirm, by opening the app on a device, whether the version that is installed is a recent build.
We are developing an iOS application for a customer who manages his apps under his own name in iTunes Connect.
I was wondering if there was a feasible way to validate an ipa when you are not the final instance which will actually upload the bundle to the App Store. A common scenario is that you deploy an application bundle to a customer so that he will be the one who manages the app in iTunes Connect, but you still want to make sure that everything checks out once the app is in your customers hands.
To be clear: we don't have access to our customers iTunes Connect but we archive the application with their distribution profile.
The idea which came to mind is to create a mock application in our own iTunes Connect without the intention to actually release the application. One could expand on this and actually do a pre-review of the app to make sure the app will not cause unpleasant surprises after we sent the archive to or customer. Will Apple throw any rocks in this path? I could imagine that they won't be happy that developers will let review the same app version twice...
You ask about whether the final Xcode archive could be tested. Yes, it can be tested. You should ask your customer to send you a copy of the submitted application, as it appears in the Xcode organizer). They would have to resign the bundle with THEIR AdHoc profile that should contain YOUR device, and send the IPA to you. You would then be able to check the final submitted app.
For the second part of your question, which is most interesting: It would be great to release the app in your account and then let the customer release it again. There are two problems: if the reviewer is the same, then your customer's app may be rejected. And: if the reviewer is not the same, it could pass validation with the first reviewer and fail with the second one.