TestFlight Builds Show “Testing” but Installation Fails – App Not Available

App Store Distribution & Marketing TestFlight
JanuaryTwelfth OP
Created
Replies 3
Boosts 0
Views 80
Participants 2

Hello Apple Developer Community,

I'm experiencing an ongoing TestFlight installation issue with my iOS app, What Should I Say?, and would appreciate assistance from an Apple engineer or anyone who has successfully resolved this problem.

App Details

  • App Name: What Should I Say?
  • Apple App ID: 6828168328
  • Bundle ID: com.wron.app0rem25mhh2
  • Version: 1.0.0
  • Affected Builds: 2 and 3
  • Device: iPhone 17 Pro
  • iOS Version: 26.6.2
  • Development Platform: Wron (Expo/React Native)

The Problem

Build 1 successfully installed through TestFlight on October 28, 2026, and I was able to use the application.

However, Builds 2 and 3 cannot be installed.

Both builds appear in App Store Connect and show a green "Testing" status. They are assigned to my internal testing group, and my Apple account is listed as an internal tester.

When I attempt to install either build through the TestFlight app, I receive the following error:

"Could not install What Should I Say?. The requested app is not available or doesn't exist."

What I've Verified

  1. My Apple Developer account is active.
  2. My Free Apps Agreement is active.
  3. Both affected builds are processed and show "Testing" in App Store Connect.
  4. Both builds are assigned to my internal tester group.
  5. My account is correctly listed as an internal tester.
  6. Build 1 previously installed successfully on the same device.
  7. The issue persists after publishing another build.
  8. The publishing interface uses the Bundle ID associated with my existing App Store Connect app.

Potential Configuration Concern

I also noticed that the project's app.json contains a different bundle identifier from the existing App Store Connect listing, although I entered the correct identifier during the TestFlight publishing process. Could an inconsistency between the configured identifier and the final signed build cause this installation error?

Assistance Requested

Could an Apple engineer help determine:

  • Why builds marked "Testing" cannot be downloaded through TestFlight?
  • Whether the builds have signing, provisioning, or bundle identifier inconsistencies?
  • Whether an Apple-side TestFlight distribution issue could cause this error?
  • What specific diagnostic information or corrective steps are required?

I have an existing Apple Developer Support case but have not received a resolution despite multiple follow-up attempts.

I would appreciate guidance on resolving this without repeatedly uploading new builds or creating a duplicate app.


Thank you.

Replies  3
Boosts 0
Views  80
Participants  2
JanuaryTwelfth OP

Additional diagnostic information:

I inspected the Build Metadata for Version 1.0.0 (Build 3).

  • Binary State: Validated
  • Bundle ID: com.wron.app0rem25mhh2
  • Build Number: 3
  • Internal Testing Status: Testing

This confirms that the uploaded binary contains the correct Bundle ID.

I've also found reports from other developers experiencing identical installation errors associated with ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING.

My external TestFlight submission has also failed with a processing error, although I have not confirmed that specific error code.

Could an Apple engineer investigate whether the TestFlight Beta Contract is missing or improperly associated with my app or developer account?

Apple App ID: 6828168328

Existing Support Case: 103013089729

Thank you.
JanuaryTwelfth OP

UPDATE: Confirmed HTTP 422 error from Apple's server

I was able to inspect the failed external TestFlight submission using Chrome Developer Tools.

The failed request returned:

  • Endpoint: betaAppReviewSubmissions
  • HTTP Status: 422
  • Error Code: ENTITY_UNPROCESSABLE
  • Title: There was an error processing your request.
  • Detail: Please try again later.

I also verified that:

  • Build 3 is validated by Apple.
  • The uploaded binary contains the correct Bundle ID.
  • Builds 2 and 3 are assigned to my internal testing group.
  • Internal installation continues to fail with "The requested app is not available or doesn't exist."
  • My Free Apps Agreement is active.

Although the response does not explicitly contain BETA_CONTRACT_MISSING, other developers have reported nearly identical symptoms.

Could an Apple TestFlight or App Store Connect engineer investigate whether my developer account or app has a missing beta contract, provisioning problem, or backend distribution issue?

Apple App ID: 6828168328

Existing Support Case: 103013089729

I can provide the complete error response and request identifier if needed.

Thank you.
Pauliver OP

I have the same problem
case ID is 30000008229837