Since the Apple Developer Site outage, we are unable to add new devices to a new or existing provisioning profile and have the app install without error to those new devices. Devices added before the recent outage work just fine with new and existing profiles, but any device added since about Saturday August 3 2013 fails, from the same file!
We have built new profiles and modified existing ones without luck. I have submitted a bug to Apple, but no response.
We distribute through TestFlight to testers, and the install works great on old devices prior to that date. However, devices added since, download the file and seem to fail at the point where the "install" takes place (ie, signature check and decryption.)
TestFlight correctly recognizes the new (and all old) devices as being added to the profile, and the installs show up properly in TestFlight on all devices as available.
My guess is that keys are being corrupted when new devices are being added to the portal.
I am looking to see if anyone else has had this problem, and if they have any kind of workaround for the issue? I have tried new profiles, new builds, new devices! Nothing works
Thanks in advance
So this problem just "went away." Apple did say they were having some problems, but the problem went away before I touched the Apple developer portal again, so not so sure.
TestFlight said they made no changes, but more research and we discovered as issue which I believe wad theirs:
Old devices still allowed the install, because they still contained old provisioning profiles from the same company (us) that covered more than one build. So any of those profiles already on the device, and the install worked fine.
New installs were not installing the provisioning profile correctly for some reason, so the installs failed because there were no old profiles. In some cases, they appeared to install an old profile that did not have the new keys, and that failed too.
We discovered that by installing a new profile by hand to new devices, all apps installed fine from TestFlight. As of last Monday though, the profiles were being properly installed again by TestFlight.
TestFlight says they changed nothing. I'm not so sure. but this problem has disappeared for the time being.
Thanks for all the answers.