Reputation: 8989
We are in a hurry to publish an app for a customer, so yesterday we published an app to App Store and now is "Waiting for review".
Meanwhile, the customer aked if he could have a preview. My idea was to send him a TestFlight beta testing. I'm thinking in several options:
What I'm not sure is on each case (internal/external testflight):
As said, the priority here is not to stop the "in review" process.
EDIT
I've been reading docs at https://developer.apple.com/library/content/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/BetaTestingTheApp.html and what makes me be scared is:
When you are done using TestFlight beta testing, you can submit the app for final review
So it seems that testflight is more like an step in the process than a parallel option in the process...
Upvotes: 35
Views: 82660
Reputation: 440
Would be nice to have had a reply after your "will give a try..."
So I had the same issues a few minutes ago:
Since the external testing will also need a review by Apple I went for the internal way. So I added my and the clients account to internal testing. Then I added the current build which is also in "waiting for review" state to the internal testing.
Result: It worked. I got the invite email and could download that build via TestFlight. The app is still "waiting for review".
Just in case someone else stumbles upon this question/answer here.
Upvotes: 38
Reputation: 1585
You always have the option to build an adhoc distribution version of your app. With this anyone who has given you there udid and it has been added to the adhoc provisioning file can install via a link or by using an .IPA file.
The major benefit of this is that the there is no review process. You build and distribute.
Upvotes: 1
Reputation: 1
As a first time apple developer publisher - I found the process rather easy than intimidating. I just had preconceived thoughts on the complexities that I would face if comparing to Google.Console publish.
What railon said is still true if not slightly improved since 2017 and should be accepted as an answer.
Upvotes: 0
Reputation: 5436
From answer at below link:
Will submitting a build for TestFlight Beta Testing stop the Final Review Test for the same build?
Apple will review as normal even with an active TestFlight and external testers using it.
What apple doc at below link says:
When you are done using TestFlight beta testing, you can submit the app for final review. Before you submit it, make sure you no longer want to test it or any builds you uploaded earlier than it. When the app becomes Ready for Sale in the App Store, testing automatically stops on earlier builds, and you will be unable to view or test them.
If you want to resume testing of an earlier build, you can upload it as a new build associated with a new prerelease version.
So, when the app becomes Ready for Sale in the App Store, testing automatically stops on this and earlier builds, and you will be unable to view or test them.
Upvotes: 10
Reputation: 1761
You can invite users to test even when the app is in review. It will not be available only when its in store.
For external testing you need the app to be reviewed by Apple just as you publish to store but for internal testing its not required.
App invite will be sent to all selected users.
Upvotes: 5