I have run into this situation a few times over the years, and haven't seen a good solution to it yet. We have distributed the live version of our application and we are working on the next iteration for release. To test it, we have our internal team using Test Flight to download the beta versions and test the new features. However, these same internal testers also have the production live version of the application that is public on their phones. This is causing a strange collision where the test version tries to use the production API url and endpoints, which causes authentication errors, which makes the testers think that the beta version is broken. We don't want to force our testers to delete the production version of the application just to test our beta version, and creating a whole other application bundle & setup (as suggested here --> https://savvyapps.com/blog/using-testflight-to-distribute-multiple-versions-ios-app) seems like overkill to me. Is there something I am missing in our configuration or settings that will allow this, or is this just not something Apple/Test Flight supports? Thanks in advance!