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...
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.