TestFlight

Review builds, testers, feedback, and crashes before the release goes out.

Bring Beta Testing Into One Place

TestFlight gathers your beta builds, tester groups, test information, and feedback. It helps you see what's available to test and turn the reports you receive into work for the next build.

Add your App Store Connect credentials in Settings, link the project in Basic Information, and upload a build through your normal development workflow. Kickstart then works with the TestFlight information Apple makes available.

Check Builds and Groups

In Builds, open a build to check its version and build number, platform, processing state, internal and external testing status, and upload or expiration dates.

This is a good first port of call when a tester says they can't see the version you expected them to use.

Groups shows internal and external groups and their testers, with available information about acceptance, installation, and testing activity. Check the group and build context before assuming feedback came from your latest changes.

Give Testers a Starting Point

Use Test Info to edit the beta app description, feedback email, and supporting URLs for the selected locale. Choose a build to edit its What to Test text, then save the relevant changes.

Be specific. "Please try importing a large photo library and let me know if progress stops" is much easier to act on than the classic "General improvements and bug fixes."

Work Through Feedback

Feedback includes screenshot and crash reports. Filter the list to focus on the kind of report you need, then turn useful feedback into a task.

Mark a report done when you've dealt with it. Show Done brings completed items back, and you can reopen one if there's more to dig into. These local workflow markers help you keep new work visible.

Export feedback to a folder or copy it when you need a record outside Kickstart. The TestFlight privacy preference in Settings can hide tester email addresses.

Review Again After Fixes

Refresh as builds and reports come in. Look for repeated issues, check the build each report concerns, and give testers a clear follow-up when you've changed the relevant behavior.

Use Release Checklists to turn a recurring beta problem into a check you won't forget before the next release.