iOS Build Environment Help Center
I've followed all the directions to install the plugin, everything works fine, the plugin generates the .ipa file. I drop it on the iTunes. Everything works correctly but the app never finish installing. The icon shows up with the tiny cloud icon as if it is being downloaded and when I click it the following message displays: Ünable to install <appname> - please try again later""
IOS SDK 14.5
Windows 10
Xcode 12.5.1
Unity 2020.3.6
iOS Builder 3.35.4
iTunes 12.11.3.17
Hello
As explained in the documentation, this symptom is typical of a wrong (i.e. refused) code signature. Either you signed your app with a distribution certificate or a distribution profile (instead of signing it with a development one), or the provisioning profile doesn't contain the UDID of the iOS device on which you try to install the app, or a mandatory entitlement hasn't been set correctly.
Have you verified all the steps in the Troubleshooting section of the documentation regarding app deployment failures ?
It is also possible that you're trying to install the app with an outdated or restricted certificate. Is your certificate valid, i.e. non expired and non revoked on the iOS Provisioning Portal ?
I started working with the iOS builder for Unity a few days ago, and I must say I'm extremely impressed by it. But I am having the same issue.
I'm very close to having everything working, and able to build and sign my app (it's just a Hello World project at the moment) using the iOS builder program. But when I try to run the deployed app on my iPad, I always get the error:
“Unable to Install [App]
Please try again later.”
I am not really sure what the problem is exactly, but I did some research and it might be due to the manifest plist file having http (not https) URLs for its assets. The URLs are local network ones (e.g.. http://192.168.1.160:5003/app.ipa). The manifest file itself is hosted on pmbaty.com over HTTPS, but the assets in the manifest are HTTP. Would this cause problems in iPadOS 14.2 that I am currently using? Do you think that updating to iPadOS 14.6 remedy the situation? I also tried syncing the packaged ipa to my iPad with iTunes, but that resulted in the same error. I'm not sure what to do.
My certificate is a temp-issued one, but I'm unsure if that is what is causing the problem. I am currently in the process of enrolling in the Apple developer program (I'm running into a problem with their certification/registration). I won't be able to test with a cert from the iOS provisioning portal until that's resolved.
What I'm using:
macOS 10.15.7
Windows 10 x64 (1809)
Xcode 12.4
iOS SDK 14.4
Unity 2020.3.11f1
iOS Builder 3.35.4
iTunes 12.11.3.17
iPad Air 4 with iPadOS 14.2
Any help is greatly appreciated, thanks.
Hello,
“My certificate is a temp-issued one, but I'm unsure if that is what is causing the problem.”
In my opinion, it is. Apple does prevent OTA (over the air) deployment of apps signed with the so-called "free" certificates generated by Xcode. OTA deployment is a feature only available to members of the Apple Developer program.
I'm confident your deployment problem should go away once you have a certificate from the Apple developer program. Let me know if that was not the case.
That was my thinking as well. But I also tried the Ctrl+C/Ctrl+V iTunes IPA installation method, to no avail. I'm still waiting for my membership order to be processed (the Apple Developer portal reads "your purchase may take up to 48 hours to process").
I'll report back as soon as it goes through and see if I can get it working.
My Apple Developer enrollment was processed today and I was able to upload my CSR to create certificate, and generate a provisioning profile through the developer web portal.
This time I had no trouble deploying the app to my iPad via iTunes (copy/paste ipa file method). It seems to be working just fine. :-)
I will have to try the OTA method later when I am on a network that I can test it properly.
Glad to hear that. If it works by iTunes, it's guaranteed to work OTA.
Regarding the fact that you couldn't achieve the same results with the free Xcode-generated certificates, considering that iOS and iPadOS have certain differences and are slowly diverging over time, it is not impossible that a bug, a problem or a clear limitation by Apple side prevents such signed apps to be accepted by iPadOS. Having no recent iPad that's something I can't verify unfortunately.
Moderators: Pierre-Marie Baty