When testing a developer .ipa file, it fails to install to a device, or appears to install but is darkened and cannot be launched.
Ensure the app is built with a developer mobile provisioning file that contains the UDID of the device you are installing to.
Determine the UDID for the device you are installing to:
- Connect the device to the computer you synch it with.
- Launch iTunes.
- Select the device and view the Summary section.
- Look for, and click on the Serial Number (this will cause the UDID to display)
- Choose Edit > Copy UDID.
- Make a copy of your developer ipa file.
- Change the extension to .zip and decompress it.
- In the resulting folder, open the payload folder and locate the viewer.app file.
- Control-click on the .app file and choose Show Package Contents.
- Locate the embedded.mobileprovisioning file and open it in a text editor.
- Search for the UDID string located earlier.
The developer .p12 file used to sign the .ipa is incorrect or contains only one certificate entry. Resolve this by recreating the certificate and ensuring only it is selected when exporting to .p12 from the Keychain Access application.
One or more web asset uses special characters, symbols, or spaces. Rename the files, fix any links as needed, and rebuild the app.
A .zip package of web assets was created from a folder. Repackage .zip files such that the source doesn't contain any parent folder, for example:
Changing the .ipa extension to .zip allows you to open it and view the Contents of the viewer.app file. Inside, you can find the file "embedded.mobileprovision" which can be opened in a text editor and searched for the device UDID.
Because filenames are used in URIs, it's best to avoid any character defined as "reserved" or "unsafe."
The DPS App Builder expects .zip files to contain root level resources. An additional container folder causes it to miss the root level .html file.