Open Radar

 
Summary:
So the problem manifests when you have a Provisioning Profile created  for Distribution saved to a local computers Xcode / Keychain. If you create a new Distribution Provisioning profile (update the original one) and do not install it, Xcode allows you to build and submit your application with the old outdated provisioning profile.

This validates fine from the Organizer App Validator, and even processing on iTunes it also validates.

The issue really came to light when after pushing a TestFlight build live, users could not install the app with the Error that the developer's certificate was out of date.

Steps to Reproduce:
1. Generate a Distribution Provisioning Profile using the normal means for an app you are going to submit to the AppStore (for testflight or submission).
2. Download this profile and install / use it.
3. Update this Distribution Provisioning Profile and do not install it
4. Archive your app and submit it to the AppStore
5. After Submission send a TestFlight 

Expected Results:
I would have expected it to fail earlier in the scene: 
In the AppStore submission verification it should check if the distribution certificates are valid and also that they are the latest available. It is likely it is only doing the "isValid" check.

On a second pass iTunes Connect should check such issues when processing the App.


Actual Results:
After a TestFlight notification, when you click install, you are given an alert that says the developer certificate is expired, please contact the developer.