Testbay

How Testbay works for iOS apps

Testbay helps developers recruit participants for an iOS beta and collect feedback. Connect App Store Connect to select a build, invite accepted participants to a private TestFlight group and check screenshot submissions. Alternatively, use manual setup with a public TestFlight link and optional in-app tracking.

App Store Connect
Private TestFlight group, email invitations, Apple tester statistics and build-specific screenshot feedback.
Manual setup
Public TestFlight link with optional native tracking for active time and named screens.
Completion
Requirements depend on the setup method. Apple statistics can be delayed and do not measure Testbay active time.

How do I set up an iOS project?

Start with a clear brief: who the app is for, what participants should try and which questions they should answer. Choose App Store Connect or manual setup. Both methods distribute the beta through Apple's TestFlight.

  1. Create a draft, choose iOS and describe the app and tasks.
  2. For App Store Connect, connect your API key, choose your app and select a build. For manual setup, provide a public TestFlight invitation link.
  3. Choose participant count, device allocations, selection mode, reward and feedback questions. In App Store Connect mode, you can also require TestFlight screenshot feedback.
  4. For App Store Connect, wait until the selected build is ready for external testing. For manual usage checks, distribute a build containing the native tracker and verify its events.
  5. Review your requirements, fund the project and publish. Open joining accepts eligible participants immediately; the application mode lets you choose who receives a place.

How does the App Store Connect connection work?

In App Store Connect, open Users and Access, then Integrations and App Store Connect API. Create a Team Key with App Manager access. In Testbay, upload its .p8 file and enter its Key ID and Issuer ID, then choose the app and build. An Admin can create the key; the Account Holder may first need to enable API access.

The private key is encrypted on the server. Apple's Team Keys apply to the apps in the account, so treat the downloaded file as a credential. Participants do not receive the API key.

Testbay creates a dedicated external TestFlight group for the listing, disables its public invitation link and attaches the selected build when it is ready. The selected app and build are locked after payment; use a new listing to change them.

Once a participant receives an active place, Testbay requests an invitation from Apple to that person's verified Testbay email. Applying alone does not trigger an invitation. A participant opens Apple's email to install the beta; no public TestFlight invitation link is needed for this method.

Which Apple statistics does Testbay show?

The TestFlight panel shows the invitation state reported by Apple, sessions, crashes, feedback counts, verified screenshot submissions and the last synchronization time. It also shows synchronization errors so missing data is not silently presented as zero activity.

Session, crash and feedback totals cover Apple's last 30 days for that participant and app. They can include activity from before the Testbay project and are not a measurement of active minutes, named screens or this build alone. These totals are informational; they are not the screenshot completion check.

Updates are synchronized periodically and the panel has a Refresh control. Apple's reporting can be delayed. An invitation request is not proof of delivery, installation or product use, and an accepted invitation is not a complete activity record.

How are TestFlight feedback screenshots verified?

In App Store Connect mode, set the required number of TestFlight feedback screenshot submissions per participant. Participants send screenshot feedback through TestFlight using the selected build, then return to Testbay to finish the brief.

Testbay counts distinct Apple screenshot feedback submissions matched to that participant and the selected build, created during their participation period and before the feedback deadline. A submission must contain at least one screenshot. Multiple images in the same submission do not count as separate submissions.

Screenshots from another build or participant, feedback submitted before the participant joined, and feedback after the deadline do not satisfy the requirement. A manual public-link listing cannot require this Apple-verified screenshot check; use App Store Connect or set the requirement to zero.

For completion, the connected build must be ready, the participant's invitation must have been requested, synchronization must not report an error, and the required screenshot count and other saved requirements must pass. Setting the screenshot requirement to zero does not create independent proof that someone installed or used the app.

When do I need the native tracker?

The App Store Connect setup uses Apple's invitation and feedback workflow without requiring the Testbay Swift tracker. Active-time and required-screen tracking are disabled in that setup method. Apple session totals do not replace those checks.

If you need Testbay active-time and named-screen requirements, choose manual setup. Supply a public TestFlight invitation link, integrate the Swift tracker from the project's setup page, report screen names when they appear and include the participant code entry flow. Upload a build containing that integration and verify the events before relying on them.

Tracker verification can report the bundle identifier, app version and build number. It confirms that events reach Testbay; it does not certify the binary or prove that every screen is instrumented. Manual setup can also explicitly skip tracking, in which case Testbay cannot verify active time or screen visits and completion follows the remaining saved requirements.

What does an iOS participant do?

The participant claims a place or applies, depending on the selection mode. With App Store Connect, they use the invitation Apple sends to their verified Testbay email. With manual setup, they follow the public TestFlight link and enter their tracking code in the app if tracking is enabled.

They follow the brief, answer questions in Testbay and, when required in App Store Connect mode, send screenshot feedback through TestFlight. The TestFlight panel lets participants check synchronization and request another invitation; the owner can also request a resend or remove an active participant from the private group.

When a project includes questions, submitted answers are reviewed automatically for relevance and sufficient detail. Answers that do not pass must be revised. This review checks the written response; it does not independently prove that someone used the product. Changing an answer clears its previous approval.

How are iOS participants paid?

You fund tester rewards for the spots you open, plus a Testbay fee that depends on whether you pay in cash or with subscription promo codes. Optional add-ons appear during setup when available. The full amount is itemized before you pay at checkout.

For a cash reward, successful completion credits the participant's Testbay balance. A TestFlight invitation alone does not trigger a reward. Requirements are evaluated using the selected setup method and the saved brief.

What happens if the build is unavailable or a deadline passes?

Keep the selected TestFlight build available for external testing. App Store Connect mode checks its processing, expiry and external-testing readiness. Apple may require beta review before the build is ready; Testbay does not replace that process. If the connection fails or Apple has not reported the required screenshot submissions, completion may remain blocked until the issue is resolved.

You fund the project before it goes live. A spot earns its reward only after its saved completion requirements are met. The cancellation and expiry flows calculate refunds for unused or unfinished allocations; completed spots do not count as unused. The testing end date, feedback deadline and any subscription redemption deadline are separate, so check the dates shown on your project.

For subscription rewards with a code redemption deadline, recruitment stops 24 hours before the code expires. Existing participants retain access and earned codes keep their original expiry. Recruitment may end earlier under the project's other rules.

Common questions

Do I need a public TestFlight link?

Not with App Store Connect setup: Testbay creates a private group and Apple emails accepted participants individually. Manual setup requires a public TestFlight invitation link.

Do I need to add the Swift tracker with App Store Connect?

No. That method uses Apple's invitation and feedback workflow and disables Testbay active-time and named-screen checks. Choose manual setup with the native tracker if you need those usage checks.

Does App Store Connect prove how many minutes someone used my app?

No. Apple session counts are delayed 30-day app totals, not Testbay active-time measurements. They may include activity before the participant joined your project.

Where should participants send required screenshot feedback?

Through TestFlight using the selected build. Testbay matches distinct screenshot feedback submissions to the participant, build and participation period. Ordinary Testbay uploads do not replace this requirement.

Why has my TestFlight screenshot not counted yet?

Apple's data may be delayed. Check the selected build, participant identity, submission time, screenshot content and any synchronization error, then refresh the TestFlight panel. A submission from outside the participation window does not qualify.

Where is the invitation sent?

Apple sends it to the participant's verified Testbay email once they receive an active place. Check that inbox and spam folder. The TestFlight panel includes a resend action.

Can I change the selected app or build after payment?

No. The App Store Connect configuration is locked after payment to keep invitations and screenshot checks tied to the promised build. Create a new listing to use another app or build.

Does Testbay guarantee App Store ratings or positive reviews?

No. Testbay collects product feedback from beta participants. Completing the brief is separate from leaving a public App Store review.

Ready to collect feedback?