I have created our .ipa (via unreal engine) and everything checks out but it will not install over to the iPhone. It just stalls with an icon that will not activate (this was done via iTunes). Worth noting from a suggestion, I used iFunbox after using iTunes unsuccessfully which actually failed instead of no error message at all as such happened in iTunes. Any suggestions? Not sure why it is failing. I have investigated the info.plist, but nothing stands out there except that the cfbundle signature is marked “???”
Everything looks fine in the log as you already know. Is it possible the device is low on space? We (and iTunes) copy the IPA over and then extract it on the device, so you will need at least twice as much space available as the IPA size is (potentially more because it is compressed).
Have you tried to deploy it to the device utilizing IPhonePackager.exe? That will potentially give us more information about what is going wrong. You can find IPP in the Engine/Binaries/DotNET/IOS directory of the engine install. Open that, hit cancel on the project dialog, go to the advanced tools tab and select install IPA to hardware. Follow the prompts and in the dos window in the background there will be a log of what it is doing to deploy it to the device. Let me know what percentage it fails at and if there is any kind of error code.
Thanks. I didn’t get the chance to test on another registered device last night, but I want to try that first. It hit me this morning…even though I own my device it is profile managed (Mobile Iron). That could very well be the problem. If I don’t see a difference in packaging I will give IPhonePackager a try. I’ll keep you posted a post results tonight. Thanks again.
Pete - See attached for the iphonepackger log. 40% Install \ Update of “Red.ipa” failed with The identity used to sign the executable is no longer valid (0xE8008018) in 16.46 secondslink text
Apple’s World Wide Developer Relations certificate recently expired. Have you installed the new one yet? (Apple PKI - Apple install the WWDR certificate expiring in 2023).
Nope, all you need to do is install the certificate from the website above on your PC and your Mac and everything else will be fine. No need to re-create any provisions or certificates.
I generated the key pairings and whatnot from scratch this time around since it had been awhile. I did this from iPhone packager (to get the csr file I believe) Not in front of me right now. Everything else was done through the apple Dev members center.
Are you suggesting that I need to update the PC in which I generated the key pairings\tried to deploy or hop over to a Mac and install the key pairings and generate from there.
I assume afterwards I need to rebuild provisions in the dev center?
No luck with the cert install. I get the same error. Install \ Update of “Red.ipa” failed with The identity used to sign the executable is no longer valid (0xE8008018) in 15.00 seconds
Actually, can you try going back to 4.10.2 and seeing if that works? This may be related to my update for signing on PC for distribution to the app store.
I didn’t have a version of 10.2 or at least I didn’t see that option. However, I installed 4.9 and ran from the iphone packager there and received the same results.
Hola Pete. Thanks for doing digging on this, as it’s a head scratcher for me as well. I came across the following:
I am not using a MAC. While I most certainly did not have previous Apple Certs on my PC (I did a reformat recently), perhaps, I need to run some new keys\key chain via iphone packager with the new cert in place. If it created the pairs without the cert maybe that is what is causing the issue?
Any rate its simple to create the necessary certs and provisions again. I will try that tonight.
Give that a try. At least your 4.9 test tells me it isn’t the new code for signing with Xcode 7. I’ll do some more research on the problem in the meantime.
So I deleted all the old certs, Identifiers and Provisions. I then created new key pairs with with 4.9 IphonePackager. I then recreated all the apple necessities. I then headed over to 4.10 and did a new rebuild with the newly created apple ID’s etc.
I then went to 4.10 iphone packager and proceeded to package…failed. Then I tried 4.9.
Success! (twice actually, as a tested this method twice. So to look at my options I tested in iTunes. For what it’s worth, itunes now works as well.
This tells me that something is still going wrong in 4.10, unless of course because I generated the keys in 4.9 there is a mismatch with trying to run from 4.10 and install. I would be happy to delete keys again to rule out via process of elimination. Thoughts?
Ok, and just to recap, you are doing a normal development IOS build on a PC and trying to get it on to your device. Not trying to do any kind of distribution build for the App Store, correct? While we have been doing that here at the office all week, it’s possible the new way of signing for distribution in 4.10.3 is causing issues with a non-distribution sign. I have another user who is having issues just get a normal sign with a shipping build (crashes trying to sign), so this may be related.
Correct. This is a normal blueprint build pushing to a IOS device as development. We’ve found its better to get it on the device working sooner than later. No distribution at this time.