I might not be the first one to ask this question but mine is slightly different from this and this
I uploaded a build for testflight review and it got approved. But now I have an improved version. I am aware that I can upload this updated version to itunesconnect.
The question is -
How long it may take to get approval for my latest build?
In case the latest build is still waiting for review, can I still continue testing (external testers) with my already approved version?
How long it may take to get approval for my latest build?
It will be approved immediately.
Once a Beta build is approved for testing, successive builds get approved immediately. In fact, at my firm, after submitting a build to the App Store, we just bump the build version & submit the app for Beta Testing to avoid Beta Review time to delay our testing.
All our Beta builds after the initial one have been approved immediately.
In case the latest build is still waiting for review, can I still continue testing (external testers) with my already approved version?
Yes, but doesn't matters coz of above^
Answer to question 1 :
It depends, how long did it take for your last build ? Did you change a lot of code ? It may vary between 2 to 10 days (approximately).
Answer to question 2 :
Of course you can, when you will want to test your lastest build, you will be asked to remove from testing the current build. This is implemented in a way that you can be waiting for review on your lastest build but still test a recent build of your application.
If you have any other question about TestFlight/Release feel free to ask but keep in mind that a lot of similar questions had already been asked/answered.
Hope it helped.
Related
I am planning to build a prototype iOS application over the course of the next few months--let's say until October 1st--that will need frequent updates for iteration and user testing. After the application is approved for Testflight for the first time, I understand that it will be online for 90 days. I need closer to 140 days.
Firstly, what is the best way to update a build without triggering a few review? My understanding is that updates would not require a review and would take 1-2 hours to become visible, but I'm not sure what process is necessary for this, and what the limitations are. Do I need to update the version number and upload in a specific spot? How do I make sure users can download the new build? Should I delete the old one?
Secondly, how do I extend the time limit beyond the 90 days?
The answers might be related.
My question is similar to this old one, but no-one answered it.
You can make "test builds" available immediately via TestFlight for Internal Testers only.
If you're trying to get it to "outside" testers, then updates will have to go through Apple review.
From experience -- if you include enough information in the Reviewer Notes field, and you are only doing incremental changes, reviews can get done very quickly.
Note that if you are "updating" a test build with a whole new section to your app, yeah, the reviewer will likely put it through its paces.
Side note: I've also found it never hurts to begin your Reviewer Notes with something like "Hi Reviewer!! Hope you're having a great day! This is a minor update for our testers, fixing a couple layout issues, typos, etc."
For your other questions... just update the version number and archive / upload it as normal. It should automatically replace the current TestFlight version (for your testers to download).
I've just published an app on Apple's store and I'm wondering about having multiple versions of the same app for testing on TestFlight. Of course dev doesn't stop when publishing... from now on I'll have to update the app store version (v1.0.0) with bug fixes (v1.0.1, v1.0.2, ...) and before doing so I'd like to check them in test flight to ensure the fix was appropriate.
My problem is that I'm already starting to develop the next version with further functionalities of the app which will become v1.1
So ideally I'd like to have my app available both for my bug fixes, for instance v1.0.2 and also my next version v1.1.0 (this will include all bug fixes made to the store version and also many new features, refactors, redesign, etc)
I know that if I build and upload to the apple store connect a build with v1.1.0 (next version) I won't be able to upload one for a built with a bug fix on the current app store version (v1.0.2) since this version would be lower than the one I uploaded (next version)
Is there a way to accomplish this? I've read this article https://savvyapps.com/blog/using-testflight-to-distribute-multiple-versions-ios-app which solution is to create extra applications in iTunes with different app ids and bind them to different certificates. But what will happen when the next release is ready to be in the store? I would have to release it and then disable the previous one? How may this affect my users? Will they have to re-install a new app rather than updating it?
I really need to start testing and checking the next release of my app in TestFlight and also support the current one with updates if something pops up. Thanks in advance!
I am able to upload multiple versions of the app to TestFlight. Each upload requires a higher version/build number, but you can switch the TestFlight test version between them as need be for testing.
Once I submit a particular build for release, however, I seem to lose the TestFlight access to the old builds.
In short, you can have many builds available in TestFlight, but once you submit the app for release, you have to start over making builds for TestFlight.
You keep talking about numbers like v1.0.1. That looks like a public-facing version string, with a major, minor, and patch number.
But that is not what TestFlight cares about. Well, it cares to some extent. But all TestFlight really cares about is that every new build you upload has a new build number. This is just an integer which you simply increment every time you submit a new build.
So you could have v1.0.1(23) on the App Store, and then on TestFlight you could upload v1.0.2(24) which starts moving forward toward version 1.0.2, but also upload v1.0.2(25) which is actually an attempt at a prospective version 1.1. TestFlight doesn't know or care what these different builds signify. They can all exist simultaneously on TestFlight. Keeping them all straight and on their individual trajectories is up to you.
My first iOS app is currently at the "Waiting for Review" stage on iTunes Connect.
Now, we are working on some bug fixes and I need to upload a new build, however, I would like to release the app as soon as possible.
My question is after an app is accepted, how long approximately does it take for Apple to review a new build / version for an app ?
Also see http://appreviewtimes.com to get an idea of current waiting times, based on developers self-reporting on Twitter.
Same as always, 7 to 10 days. Except when you ask for an expedited review, but then you should have a really good reason (and a really popular app ;-).
Any time you change your binary you go back to the end of the review line. The time varies depending on how busy the review team is.
The bulk of the time seems to be in "waiting for review." The actual review process seems to be pretty quick, assuming they don't need more info from you to make their decision.
The process of getting fixes to a rejected build seems to be faster than the original review process.
I would suggest planning on an app review taking 10 days. It might take less time, but that seems to be fairly typical.
94% of all iOS app updates are reviewed within 5 business days at the moment.
You can always check https://developer.apple.com/support/app-store to get the latest info on that.
First of all I want to thank all of you for this great community. I started coding my app in March of this year with zero experience and just yesterday my app was approved for the App Store.
I have a pretty tight release deadline being the first of September so I'm happy that my app is already Ready For Sale. Since my app submission I made some minor changes to the UI and corrected some spelling errors so it's really nothing dramatic but I'd like to update it before release.
So my question is, is there any problem uploading a new version when I haven't released anything so far? I don't want to lose the Ready For Sale approval for my first version, just in case anything would go wrong during the review process.
Thanks for your help :)
You can submit your new version of application .It will not affect your current version of application.If application will be approved then old one will be removed from appstore and newer one version will be ready for sell .If New version will not be approved then old version will be ready for sell.
Currently an update to my iPhone application has been in review for over 10 days!!!
In that period of time I've been able to work out a few bugs and even add some small new features to my application. I know that it is possible to reject your binary, but I would rather go a head a publish my application then send apple a better version 1.1.1...
So basically my question would be if I rejected my apps binary and submitted one right after would my app get pushed to the bottom of the review pile or would I keep my spot in line (since I've already been waiting for 10 days)?
No, rejecting a binary and immediately resubmitting a new one will not maintain your place in line: you would be knocked back to the start of the queue. I base this on my own experience, having rejected and resubmitted binaries a few times in the past.
Now, you might be thinking: "OK, what about the expedited review process?"
I can share some experience with that: With my latest app, I was in the same position you were in but I decided to go ahead and release 1.0 and then submit 1.0.1 soon afterwards. When 1.0 was approved and released, Apple chose it for the "New & Noteworthy" section. All of a sudden the app was getting a lot of exposure—and complaints about a bug that I had fixed in 1.0.1. I submitted 1.0.1—and as well as a request for expedited review—which was approved. 1.0.1 was released about 24 hours later.
So, you'll have to weigh the pros and cons for your own app, but I hope this info helps. :)
Yes it would, rejecting and resubmitting the binary will place you at the bottom of the review queue. It's unfortunate, but there is no work around.
If Apple allowed that then many devs would start uploading their beta version while trying to fix those last few bugs.
I had the same issue. I had submitted my app and it was in review. I was asked to change some metadata and resubmit the app. While doing that, I discovered a UI issue and fixed it. I was in a dilemma as to keep the current binary and release a version 1.01 or upload the new version. I did not want to send my first app with an issue so, I went ahead and rejected the binary and uploaded the new one. I immediately contacted Apple developer technical support. They claim that "The review time will not be affected and that our internal systems do have process your build before it can be reviewed (verifying it’s general correctness and resigning your app for the store), which can add some delay. However, that delay is fairly small and is only a minor factor in review time. More to that point, any delay here is much smaller than the delay of a new submission." I hope that is true and hope my app is not stuck in the "waiting for review or in review" limbo :(.