App Store releases of the same or greater build should automatically over-write Test Flight beta installs.

Originator:padraig.kennedy
Number:rdar://19666318 Date Originated:30-Jan-2015
Status:Open Resolved:
Product:iTunes Connect Product Version:
Classification:Enhancement Reproducible:Always
 
Summary:
TestFlight betas expire after 30 days, so all of our testers will be locked out of our app once it expires. The App Store version of the the same build has been approved and is on the store, but it doesn't auto-install over the TF build. I think it should. It's the same build and it won't expire. 

This issue will lead developers to constantly re-issue unchanged TF builds to keep their testers happy, or to have to implement custom communication telling their testers to jump in and out of the test. 

If I subsequently release a new beta, the user can be notified and then choose to switch back to that.

Steps to Reproduce:
1. Release a TestFlight beta
2. Test and confirm the build works as expected
3. Submit for review, get approved.
4. Wait 30 days.

Expected Results:
I expected that when the app store version was approved, it would install over the Test Flight beta with the same build / version number.

Actual Results:
Test Flight beta expires and beta users' apps simply crash on launch. Users are confused, likely to delete and re-install (losing data), and nervous about joining future betas.

Version:
iOS 8.1.3

Notes:
Only work around is to avoid the 30 day limit by continuously re-submitting the same build to testers every 30 days.

Configuration:


Attachments:

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!