How to Test Your iOS App with Testbay and TestFlight
By Testbay
Testbay helps you find TestFlight testers and collect feedback around a clear task. You can connect App Store Connect for private invitations and build-specific screenshot feedback, or use a public TestFlight link with manual setup and an optional native tracker. Both distribute the beta through TestFlight, but they verify different things.
If you are asking “How do I find test users for my TestFlight?”, start by making sure the build is accessible and the brief explains what you need to learn. Recruiting people cannot fix a build that nobody can install or an app that requires credentials you forgot to provide.
Prepare a task before you recruit
Choose one flow that matters: finishing onboarding, creating the first project, recording a workout or finding a saved item. Describe the task without explaining every tap.
For example, “Create a plan for your next week and tell us where you hesitated” is more revealing than a list of buttons to press. Include device needs, account access, estimated effort and any data participants should use. Fictional data is often enough for a beta task.
Then choose participant count, reward, feedback questions and whether participants join immediately or apply for your approval. If you need people with a particular use case, use the application flow and select for that need.
Option 1: connect App Store Connect
In Testbay's iOS setup, connect your App Store Connect API credentials and select the app and build. The setup guide explains the Team Key, App Manager access, Key ID, Issuer ID and .p8 file you need. The private key is encrypted on the server and is not shared with testers.
Testbay creates a dedicated external TestFlight group for the listing, disables that group's public link and attaches the selected build when it is ready. Once a participant receives an active place, Testbay requests an Apple invitation to their verified Testbay email. Applying alone does not send an invitation.
Apple's external-testing requirements still apply. Make sure the selected build is ready for external testing before relying on recruitment. See Apple's external tester instructions for the current Apple process.
The selected app and build are locked after payment. If you want to test a different build through this workflow, create a new listing.
What App Store Connect feedback verifies
You can require a number of TestFlight screenshot-feedback submissions. Testbay counts distinct Apple submissions matched to the participant and selected build, made during their participation period and before the feedback deadline. Each counted submission must contain a screenshot. Several images in one submission count as one submission.
This is useful when you want feedback tied to the build people were assigned. A screenshot from another build or before the person joined does not meet that requirement.
The dashboard also shows Apple's invitation state, sessions, crashes, feedback totals and synchronization status. Those statistics can be delayed. Session, crash and feedback totals cover Apple's reporting period for the participant and app and can include earlier activity. They are context, not Testbay active minutes or proof that a specific screen was visited.
This setup does not require the Testbay Swift tracker. Active-time and required-screen tracking are disabled in App Store Connect mode. If those checks are important to your brief, choose manual setup instead.
Option 2: use a public TestFlight link
With manual setup, supply the public testflight.apple.com/join/... link. Participants use it to install the beta. Make sure its group and build settings allow the people you recruit to join.
If you need time and screen requirements, integrate the Swift snippet from your Testbay setup page into the app. Add the participant-code entry flow and report stable screen names when those screens appear. Distribute a build containing that integration, then use Testbay's verification step to confirm events arrive.
Participants must enter their own assigned code in the app. Your owner verification code is for checking the integration, not for everybody's sessions. Required screen names need to match the instrumented names exactly.
Manual setup can also explicitly skip tracking. That makes setup lighter, but Testbay then cannot verify active time or screen visits. Completion follows the remaining saved feedback and submission requirements.
What the participant does
With App Store Connect, the participant accepts Apple's email invitation. With manual setup, they follow your public TestFlight link and, for tracked tests, enter their participant code.
They try the requested flow and submit the required feedback. Apple screenshot feedback is sent through TestFlight where required. Written answers and native-test design proposals are submitted through their Testbay session page. The native tracker does not add the website's floating feedback widget to your app.
Ask about concrete moments: what they expected after tapping a control, which permission request needed explanation, or what stopped them from reaching the first useful result. Do not make the beta task depend on purchasing a real subscription merely to reach the feature you want tested.
Completion and rewards
The saved requirements determine completion. Written answers must pass automatic review when questions are present; that review checks the response, not whether the app was independently used. The relevant tracking or App Store Connect requirements also need to pass.
Cash rewards credit the participant's Testbay balance on completion. Subscription rewards require a supported web-based Stripe checkout and redemption page. They are not Apple in-app purchase codes and do not automatically unlock an App Store entitlement. Make sure the web subscription actually gives access to the app account you advertise.
For the exact setup screens, see how Testbay works for iOS apps. When the build and brief are ready, create an iOS test and recruit around the flow you need to improve next.
Put the feedback to work
Choose one product question, write a focused brief and offer people a reason to help you answer it.
Create a brief