Hi everyone,
I’m encountering a persistent issue with a visionOS app distributed through TestFlight for internal testing.
The Problem: I have successfully archived and distributed the build as an Internal Test. The testers (including myself) received the invitation, accepted it, and the app is visible in the TestFlight app on Apple Vision Pro. However, the moment we click the "Install" button, an alert pops up saying:
"The requested app is not available or doesn't exist."
Context:
Platform: visionOS (Targeting Vision Pro).
App History: This is an ongoing project where the last distribution was about 5 months ago. The app has never been submitted for formal App Review or public release; it has only been used for TestFlight.
Account Status: All agreements (including the Paid Applications Agreement) are active and in effect.
What I have tried (but did not work):
Re-uploading builds: Increased both version and build numbers and re-archived.
Resetting Test Groups: Deleted the existing internal testing group, waited, and created a new group to re-invite testers.
Tester Association: Removed all testers and re-added them to force a new invitation email.
Device-side: Signed out and back into "Media & Purchases" on the Vision Pro.
Key Observation: To determine if it was a project-level configuration error, I created a completely new App Identifier (Bundle ID) for the same project code and uploaded it as a new app record. In this case, TestFlight worked perfectly, and I could install the app without any issues.
This leads me to believe that the original Bundle ID is stuck in some kind of "detached" or "stale" state on the App Store Connect backend.
Has anyone experienced a specific Bundle ID being "corrupted" in the TestFlight system after a period of inactivity? Is there a way to force a full reset of the TestFlight status for an existing app record, or is this a backend bug that only Apple Support can resolve?
Any insights or workarounds would be greatly appreciated.