Tester: check for a newer build before deleting anything
Open TestFlight and check whether the app has an available update. Record the expired build number and the exact message before contacting the developer. Ask whether a replacement is assigned to your group and whether you should use a new invitation. Keep any screenshots or notes from the earlier session so useful feedback is not lost.
Do not assume deleting and reinstalling will restore access or preserve local app data. If you cannot see a replacement, the developer needs to check distribution. A public App Store version may exist, but it can differ from the beta task you agreed to test; confirm the intended version first.
Developer: separate expiry from other access failures
In App Store Connect, open the app, select TestFlight and inspect the intended build’s status and availability. Apple’s normal testing window is up to 90 days. A developer can also expire a build manually. An unavailable invitation, missing group assignment or review issue needs its own check; do not diagnose every failed install as the 90-day limit.
Upload a replacement when the old build has reached its testing limit, allow it to finish processing, and assign it to the intended group. Follow the current external-testing review requirements shown in App Store Connect. Confirm that a suitable external tester can actually install it before announcing that the problem is fixed.
Record the blocked participant’s context
Ask for the invitation route, build number if visible, device and the message shown. Keep personal account details out of shared reports. Compare the tester’s experience with the current group and build state. Do not promise that every invitation remains usable indefinitely; include a planned testing window and check availability before sending a new batch of links.
Publish or assign a usable replacement
Confirm that the replacement build reaches the intended external group and has the required review status. Validate installation as a fresh tester. If the replacement also changes product behavior, update the brief and mark the reports by build. A tester’s observation about build 10 should not be merged silently with a later report about build 12.
Reset the task fairly
Explain what changed and which part of the assignment needs repeating. Preserve useful work already submitted, and do not classify an access failure as a negative public opinion. Recheck the distribution conditions rather than adding rewards to solve an access problem. A short follow-up focused on the unavailable journey is usually more useful than making every participant start the whole research plan again. Identify both the replacement build and the task so old reports remain interpretable.
Working example
Recovery note example: ‘The previous beta build is no longer available. Build 12 is now assigned to the testing group. Please install it and repeat only the saved-list task; your earlier onboarding observations remain in the report. Include the new build number.’ Send this only after verifying that the new build is available to the group, not merely uploaded internally.
Your next steps
- Check the console’s current build and group state.
- Verify the replacement with an external tester.
- Label all reports by build.
- Repeat only the work needed for the next decision.
Official sources
Sources checked October 17, 2026. Review the current provider documentation before acting on requirements.
Turn the next test into something useful.
Publish a focused brief on RateMyApp. Credits fund approved private reports; public store reviews are voluntary and unrewarded.
List your app for feedback