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.
Oh yeah, whoops! Bumped the build, it should be the same in both now.
Normally the deployment strategy is to merge the TestFlight tagged code into master once we’re ready to submit, then rebuild from master and submit that build–it’s a “different build” but the exact same code. This time we ran into some Apple Review snags (they wanted a way to permanently delete your Lemmy account from within the app), so we had to hotfix that on master and forgot to release that to back to the TestFlight.
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?
