Open Radar

 
Summary:

A provisioning profile created manually via the developer portal or automatically with Xcode can expire before the certificate used to create it.

For example, this provisioning has expired:

http://files.iconfactory.net/craig/bugs/Expired_Provisioning.png

But the certificate used to create it has not:

http://files.iconfactory.net/craig/bugs/Valid_Certificate.png

Steps to Reproduce:

1. Create a certificate using the developer portal.
2. Create a provisioning profile using the developer portal.
3. Wait a year.

(The files downloaded from the portal are attached to this bug report.)

Expected Results:

The certificate should expire at the same time as (or before the) provisioning profile.

Actual Results:

The provisioning profile expires before the certificate. This breaks both internal and external builds, causing general havoc.

Notes:

The portal is as confused as this developer: the status for the expired provisioning is both Active and Expired.

Even a fastidious developer will get tripped up by this if they add the certificate expiration date to their calendar. Many do this because we not only deal with certificates for apps, but also for web sites where SSL and push notification services are deployed.

Describe circumstances where the problem occurs or does not occur, such as software versions and/or hardware configurations.

----

Attached are two files:

Iconfactory_Distribution.cer which expires on 1/13/2015 at 8:05:10 AM PST
Iconfactory_App_Store_Distribution.mobileprovision which expires on 1/12/2015 at 12:04 PST

Want to bet someone is using local time and someone else is using GMT?