Archiving and uploading a build to TestFlight
the release-build distribution flow.
select a real-device or Any iOS destination, Product Archive, then in the Organizer distribute to App Store Connect, where the build appears for internal TestFlight testers after processing.
What's really being asked
The interviewer wants to confirm you have shipped a build and understand the sequence from local archive to a tester's device through TestFlight.
The full answer
First set the run destination to a generic Any iOS Device or a connected physical device, because archives are built for device architectures, not the simulator. Ensure the version and build number are set, incrementing the build number so it is unique. Choose Product then Archive, which builds in the Release configuration and produces an archive that opens in the Organizer. In the Organizer select the archive, click Distribute App, choose distribution to App Store Connect, validate, and upload. Xcode signs the upload using a distribution certificate and an App Store provisioning profile. After upload, App Store Connect processes the binary; once processing completes the build appears under TestFlight. Internal testers, who are members of your team with the right role, can install it immediately, while external testers require a Beta App Review.
The mistakes people make
Trying to archive while a simulator is the destination, which Xcode does not permit. Forgetting to increment the build number, causing an upload rejection for a duplicate. Confusing internal testers, who get builds immediately, with external testers, who need review.
What usually comes next
What is the difference between internal and external TestFlight testers? Why must the build number be unique? What signing assets does the upload require?
A concrete example
You set the destination to Any iOS Device, bump the build to 42, and run Product then Archive. The Organizer opens with the new archive; you click Distribute App, pick App Store Connect, and upload. A few minutes later App Store Connect shows build 42 finishing processing under TestFlight. Your QA teammates, added as internal testers, open the TestFlight app and install build 42 right away to begin verification, with no external beta review required.
Interview question
Why must you select a device or Any iOS Device destination rather than a simulator before archiving?
- a.The Organizer is disabled while a simulator is connected
- b.Simulators cannot run the Release configuration
- c.TestFlight only accepts builds compiled on physical hardware
- d.Archives are built for device architectures, which the simulator destination does not produceCorrect
Why? this is the answer
An archive must contain a device build, so Xcode requires a device or Any iOS Device destination; the simulator target produces simulator binaries that cannot be distributed. The other options misstate how configurations, hardware, and the Organizer work.
Just read this? Test yourself on what you have been reading.
Read the original → developer.apple.com
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on ios — each one lists the topics its interview covers.
See open roles