Post #2226758
2026-04-29 08:46 UTC
Are you using TestFlight as a developer?
How do you deal with the following situation:
You've run a successful beta cycle on TestFlight and have now released the final product in the (Mac) App Store. But your TestFlight users are still on the beta track, and their app eventually gets disabled after 90 days. They get confused because they're not getting any idea that they have to drop the TF app and instead re-install the app from the Store.
Can that be avoided or resolved more elegantly?
Replies (2)
-
@teilweise@layer8.space 2026-04-29 09:03
@tempelorg@iosdev.space For me as a user of apps on TestFlight, the switch from TestFlight to AppStore is not the big problem. Manual step but it works. The bigger problem is after that: I was on TestFlight, the beta expired, I switched to AppStore version. Now the app is no longer visible in TestFlight (!). Even if a new build becomes available, I no longer get notifications because the installed version is the AppStore one. If possible: Upload new (unchanged) builds to TF regularly.
-
@joshua@social.tupo.space 2026-04-29 10:28
@tempelorg@iosdev.space I tend to release fake beta builds every 85 days to keep users on the beta train.