The way we resolve this is by closing/pausing two tracks. The internal testing track enables us to create and manage internal testing releases to make the app available to up to 100 internal testers. It's more than sufficient at this point. And having four tracks just adds to overhead of releasing it to four tracks.
One closed testing track is closed and open testing track is paused. So similar to test flight, we release internally and we release it to the public.
The way we resolve this is by closing/pausing two tracks. The internal testing track enables us to create and manage internal testing releases to make the app available to up to 100 internal testers. It's more than sufficient at this point. And having four tracks just adds to overhead of releasing it to four tracks.
One closed testing track is closed and open testing track is paused. So similar to test flight, we release internally and we release it to the public.
Active
Stopped track
**Paused track***