I am trying to package my UE4 4.11.2 project for iOS on the computer with windows 10. I have successfully packaged iOS packages in the past, but all of the sudden, all provisions and certificated went invalid. I was able to get one of my developer certificates valid again, but not my new one. Also, all previous provisions still state ‘No valid certificate found’ as status; Even when bundle ID match and the correct certificate is valid.
I made my provision and certificate on Macbook Pro and emailed them and the key (.p12) to my email address, so that I could continue my UE4 editor on windows 10 to package my new project for iOS. I get this message every time I try to import the certificate. Failed to load or install certificate due to an error:‘Object reference not set to an instance of an object.’ I can no longer package for iOS on my windows for either certificate…
I have seen answers where the date has solved this problem or the bundle id was incorrect, but this is not the solution for my problem… Any ideas? I have messed with this for too long now and need to get this working again…
Since you made your provision and certificate on a Macbook Pro and they are causing issues on your Windows 10 machine I recommend following this guide to install your provisions and certificates directly from Apple to that specific system:
Also, I have had success in the past with provision and certificates generated on my macbook. So because I currently have my old certificate and provision working with the “change the date” hot fix. I don’t want to try to regenerate the new certificate and ruin the valid old one.
Is there a reason to believe that the Macbook generation of the certificate would be the problem? Please advise.
Unfortunately not, I exported the .p12 file from keychain and sent it over as the documentation recommends. I appreciate the thought though, but this is not the solution.
UPDATE:
I still have only one of my iOS certificates valid (white not green) and still receive the error message when trying to import another. All of my provisions still say No valid certificate found, but when changing the date like mentioned in other posts the status does change, but not to working. After changing the date backward about a month, most say expired, some say identifier not matched but they are not the correct provision for this project so I dont want to match the identifier. When I change the date forward a month, they all still say no valid certificate found.
With all changes my certificate stays valid and white now.
I have tried creating new provisions and importing them and tried re-downloading the old provision. What needs to happen to get this working again???
I feel like there is something in my system settings still directing them to an old certificate? Does anybody know how to change this?
Try downloading and installing the AppleWWDRCA from step 5 in the following link: iOS Dev Center
For Windows: download, right-click, and choose “install”
This will update your Apple Worldwide Developer Authority Certificate if it has expired, which I expect may be the case since you stated initially that your provisions and certificates became invalid “all of the sudden.”
Hi. I was just having this exact problem and I have a solution that might work for others if you find yourself in the same situation. When creating my .p12 file I chose not to password protect it, by just hitting enter twice when prompted to create a password while generating the .p12 file. Worked just fine after that.
This no longer works. When building with a certificate imported with a key without password protection, the build process is stopped and a security warning displayed. So this is no longer allowed.
