legacy ios build issue

[Philip_B_1]

When I attempt to perform an OTA installation of a legacy, ios ad-hoc build, I keep getting the popup message that the app "could not be installed at this time."

This occurs on two different iphones. The app was successfully built and installed OTA over a year ago. Since the certificates had expired, I generated new ones and uploaded them in the build tab of the XDK. The build completed without error.

I also downloaded the ipa file and installed with iTunes. The installation left a darkened icon that when tapped showed a progress circle that appears to go to completion but then pops up the same message that the app "could not be installed at this time."

I'm not sure how to proceed now. Remake the certificates and reinstall them? Could someone confirm the legacy ios ad hoc builds are running properly? Thanks.

[Amrita_C_Intel]

Try Cordova build instead of legacy!!

[Amrita_C_Intel]

And try to follow these steps

https://software.intel.com/en-us/xdk/docs/building-cordova-ios-apps-intel-xdk

[Anusha_M_Intel1]

Hi Philip,

I faced a similar issue on Android. It turned out to be because there was another app on my device with the same App ID. It is worth confirming this isn't the case.

[Philip_B_1]

Amrita, I've rebuilt the app with Cordova instead of the legacy system and the same "could not be installed at this time" message pops up in the OTA install here too.

All previous versions of the app were deleted from the phone. This app was successfully built and installed several times last year. Short of remaking my ios certificates again, I'm not sure what to check now. 

[John_H_Intel2]

What OS version are you building for?

What OS is your device?

Is the device UDID in the provisioning profile you are building with?

[Philip_B_1]

John,

I finally got the app to install. I had two problems. The legacy build didn't install for any of the devices in the provisioning profile. But when I moved to the Cordova build, I only tested on my personal device and the UDID was not reported correctly by the reader utility I used. The build did install on other devices in the provisioning profile. And after correcting the UDID error, on my personal device too. Thanks for your help.

Phil