TestFlight Installation Fails for All Apps in Account (“App Not Available” Error)

App Store Distribution & Marketing TestFlight
Muhammed_Yilmaz OP
Created
Replies 1
Boosts 0
Views 121
Participants 2

Hello,

I’m experiencing a serious issue with TestFlight.

I correctly set up internal testing:

•	Added testers via email
•	Assigned builds
•	Everything shows as “Ready to Test”

However, when trying to install via TestFlight, I get:

“App Name couldn’t be installed” “The requested app is not available or doesn’t exist”

⚠️ Important note: This issue is NOT limited to a single app. It happens across all apps in my account.

So it does not seem to be app-specific.

What I’ve already checked:

•	Agreements, Tax, and Banking are completed
•	App Privacy is fully filled
•	Builds are successfully uploaded and selected
•	I am correctly added as an internal tester
•	Tried logging out/in of TestFlight
•	Reinstalled the app and TestFlight

I contacted Apple Developer Support twice but received no response.

Has anyone experienced this issue affecting multiple apps? Any help or guidance would be greatly appreciated.

⸻

Additional technical details:

• Developer Account Apple ID: yilmaz34muhammed(at)icloud.com

•	App Store Connect App ID: 6762088121
•	Bundle ID: com.devyilmaz.TahlilAI
•	Build Version: 0.2.0 (1)

This issue occurs across all apps in my account.

Replies  1
Boosts 0
Views  121
Participants  2
paoloacx OP

I'm having the same problem with all my apps, not just one. Internal TestFlight builds fail to install on both my iPhone and iPad. On the iPhone, the error is "The requested app is not available or doesn't exist"; on the iPad, it says "Try again later", and tapping "View" does nothing.

I've checked that the builds are assigned to the internal testing group, show as Testing and haven't expired. My tester account and developer agreements are active. Restarting the iPhone and switching from Wi-Fi to cellular data made no difference.

I contacted Apple Developer Support on November 3 and received an acknowledgement, but no further response so far. Has anyone had this resolved by Apple?