TestFlight: "The requested app is not available or does not exist" for internal testers + 422 ENTITY_UNPROCESSABLE on beta review (new individual account)

New individual account (Team ID UTH8X8R54P). App ID 6825129426, bundle com.lichooo.inercia.

Since Oct 20, every processed build (latest 1.3.0 (7), uploaded Nov 2) fails to install for internal testers with "The requested app is not available or does not exist", including the account holder, whose Apple ID matches the one on the device. Submitting any build for external beta review returns 422 ENTITY_UNPROCESSABLE "Please try again later" (error IDs a82b110f-0641-44db-af8e-7452cb4bf93c and 4115b133-61c0-4135-9306-ba4bbe51514e).

Already checked:

  • Latest Program License Agreement and Free Apps Agreement accepted (Active)
  • EU DSA trader status completed
  • Export compliance answered (no non-exempt encryption)
  • Test Information complete (description, feedback email, privacy policy, contact, review notes)
  • Internal tester status Accepted, internal build state IN_BETA_TESTING
  • Re-uploading builds and reinstalling TestFlight didn't help

Support cases 103003383660 and 103004342314 are open with no resolution, and phone support is currently unavailable.

Could someone from the TestFlight team check whether the account is missing the beta agreement (BETA_CONTRACT_MISSING) or has a backend flag? Thank you.

I'm facing a very similar issue, affecting every application under my Apple Developer account.

Internal TestFlight installations consistently fail with "The requested app is not available or doesn't exist", and I am also unable to proceed with External Testing.

All agreements and memberships are active, and everything was working correctly before the issue appeared.

I have checked the browser developer tools and did not observe BETA_CONTRACT_MISSING during my investigation.

Despite opening a support case and sending follow-up messages, I have received no response from Apple Developer Support.

Apple Support Case ID: 103016687952

This is now blocking testing and development across all my applications.

Could an Apple engineer please investigate whether this is a wider TestFlight backend or account-level issue?

Has anyone received an official response or solution from Apple?