I'm concerned that this would only add more opacity. If I were to use a library for navigation, I think it would be preferable to use something based on simpler primitives like queues.

But we will be able to publish the app to the app store when visionOS 2.0 is officially released. It's still important to be able to distribute apps for internal testing via TestFlight while it is in development. The error message says "Although you can use beta versions of SDKs and Xcode to build and upload apps to App Store Connect..." and yet it fails when I set the release type to Internal Testing Only.

Ah I see. I may be misunderstanding the API then. We are using Auth0 to authenticate, and they tell us they use the ASWebAuthenticationSession to log in, and I don't know exactly how they are doing Logout but they said they are clearing the session token from the cookie jar. What is the recommended way to invalidate a session token (or otherwise log out a device) obtained via ASWebAuthenticationSession?

Apple prevents my apps from taking existing names even before my App is in the app store. If the whole set of released + unreleased app names must have 0 collisions, then I may not know who to contact for the right to the name of an unreleased app. Of course it's also possible that only released apps block unreleased ones and not vice-versa.