Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My TestFlight beta stopped working for testers after 90 days

Short answer

Apple lets you test a TestFlight build for up to 90 days, after which it becomes unavailable to testers. To continue, upload a new build with a new build number and add it to the groups. Ask your developer to note the expiry date of each beta build so it is renewed in time.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Testers say the beta will not open any more.
  • TestFlight shows the build as expired.
  • The app worked for months and then suddenly failed for everyone at once.
  • There is no newer build in TestFlight.
  • Nobody remembers when the beta was uploaded.

Why does this happen?

  1. Builds have a fixed testing period

    Apple says you can test a build for up to 90 days. After that the build becomes unavailable to testers.

  2. No newer build was uploaded

    Testers stay on the old build until a new one is added to their group. If the team stopped releasing, the last build runs out.

  3. The build was stopped on purpose

    Apple says you can expire a build earlier using the stop-testing option. Someone tidying the list may have done it.

  4. Group insight cards were ignored

    Apple says the group page shows cards that flag builds about to expire. Without anyone checking, the warning goes unseen.

  5. A production release was assumed to replace it

    Apple says that if a build goes to the App Store without being expired, invited testers can still test it after it goes live. The beta and the live app are separate things.

What can I do about it today?

  1. Confirm it is the 90-day limitOpen TestFlight in App Store Connect and check the build status and upload date.
  2. Ask for a new buildYour developer must upload a new build with a new build number and add it to the groups.
  3. Tell your testersA short message that a new build is coming spares them from reinstalling and reporting.
  4. Add the next expiry date to a calendarSet a reminder shorter than the limit, shared with a second person.
  5. Do not delete the app from testers' phones yetLeave it until the new build is available, so feedback history stays in place.

When should I bring someone in?

  • Nobody can build the app any more.
  • The app was built long ago and will not compile with current tools.
  • You need testers continuously and have no release routine.

How do I handle it?

  1. Check the old buildI look at the build status, upload date and groups before changing anything.
  2. Rebuild and upload a new oneA new build with a new number goes to App Store Connect and into the same groups.
  3. Handle review if neededExternal testers may need Apple's review for the first build of a version, so I plan for it.
  4. Set a renewal routineA regular, short release rhythm keeps the beta from lapsing.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Can I extend the 90 days?

The Apple page I read does not offer an extension. The way forward is a new build.

Do testers lose their feedback?

The page does not say. Ask your testers to send important feedback before they switch.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.