I would like to bring to your attention that packaging for IOS is broken in terms of cert validation checks.
I am not sure where the certificate needs to check the time but it appears as if it is trying to do so in a different time zone.
My cert was issues at 4pm and when trying to use this certificate with UE4 i am getting a message stating that the time in UTC is now only 12pm.
As you can imagine i do not wish to wait 4 hours every time i switch certificates just to deploy to a device.
If there are any workarounds for this it would much appreciated if they are communicated.
This problem did not exist prior to 4.5 which makes me believe somewhere something must have changed during the update.
I believe this is strictly the way you do cert validation checks.
Please have a look at these and let me know if you need any other ones.
Also i made another post but will delete it.
I can no longer package for IOS.
It keeps failing now. And when assigning a new provision profile i get those issues as posted above in the screenshot about the UTC time.
Other post stated
What is strange is that it states during the build Found matching certificate 'iPhone Developer:
But after it fails it says
Device ‘blah blah’ is being checked against . <— why is this blank? Should it be blank? Please guys. I am on the verge of launch and now i am no longer able to test on mobile.
I checked all certs. I logged another bug where its doing validation checks against UTC time and not my current time. Was this hard coded with the new release?
Hi Sean. I am liaising with another Epic member.
This was discussed but i am still unclear regarding the UTC time conversion and the problems that poses.
ok. I found why the build was failing. The images in the Build\IOS\Resources\Graphics caused this After i deleted them did the build start working.
Build\IOS\Resources\Graphics Default-Iphone6.png Default-Iphone6Plus-LandScape.png Default-Iphone6Plus-Portrait.png
However now im confused about how to get Iphone6 splash screens. But lets not detract.
I would like to confirm if it converts to UTC time… do i really have to wait 2 hours for a brand new cert before it becomes active according to the check?
I think how its being converted is faulty. It should take into account the local time or do a check against a TSA (time stamping authority) of sorts.
I am only 2 hours. But there are people 13 hours +UTC