Expired Test Flight builds should inform the user why they can't launch instead of just closing.

Originator:padraig.kennedy
Number:rdar://19666485 Date Originated:30-Jan-2015
Status:Closed Resolved:16-Jul-2015
Product:iTunes Connect Product Version:
Classification:UI/Usability Reproducible:Always
 
Summary:

When a Test Flight build expires and a user tries to open it, the app looks like it’s launching and then closes. This appears to the user like a crash. There’s no hint about what has happened however, so a user will not know to either install the app store version or wait for a new release.

Steps to Reproduce:
1. Release a TF beta.
2. Let it expire after 30 days.
3. Try to launch it.

Expected Results:
iOS should notify the user that the app has expired.

Actual Results:
The app appears to crash.

Regression:
Always happens.

Notes:
See also radar #19666318 - not fixing this issue will lead developers to continuously re-submit the same unchanged build, just to get around the expiry time limit.

Comments

Fixed in iOS 9

By padraig.kennedy at July 17, 2015, 12:18 a.m. (reply...)

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!