Would it be possible to update the TestFlight build whenever a new build is pushed to the App Store? This way, TestFlight users won’t have to switch to the App Store version because the TestFlight version would always be at least as new.
Would it be possible to update the TestFlight build whenever a new build is pushed to the App Store? This way, TestFlight users won’t have to switch to the App Store version because the TestFlight version would always be at least as new.
Why not just use the stable App Store version instead of the bleeding edge Test Flight build? Isn’t Test Flight for testing purposes and hence likely to contain more bugs? Fixes should be merged back into the stable branch.
Yes it’s for testing, but there’s not much point in testing an outdated build.
Right, but there’s a stable release. If there’s more issues to test, there will be a new test flight. Why have stable builds released under test flight?