In-House application disappears after installation

I am currently creating an iPhone application for a client that will be distributed internally. My client just created his developer account at Apple.

I created a website so that the client downloads test versions of the application wirelessly using the instructions given here: Distributing corporate applications for iOS devices 4. These tests were performed through my standard account using the Adhoc profile that specified it UDID for development.

Now I'm trying to deploy the application using my "Enterprise" account. I created an initialization file internally. I also created an application archive and created an .ipa file for distribution using this profile.

The problem that I am encountering occurs when I try to download the application. When I go to the site that I created to download the application, I see the application downloaded on my iPhone, according to the inscription: "Loading ...". Then the text will change to "Installation ...". As soon as the progress bar ends, the application disappears. I also noticed the embedded provisioning files installed on my device.

I repeated the process several times on several devices, both devices that I used to test this application, and those in which I did not even use this application. I even tried to delete all initialization files on one device. The same process occurs and the internal provisioning file is automatically installed automatically.

What exactly is wrong or am I not doing?

Thank.

+45
iphone provisioning-profile enterprise wireless distribution
Apr 09 2018-11-18T00:
source share
6 answers

I had the same problem with one of my internal applications. The reason was that the package identifier in the application manifest was not specified correctly. After I set the package identifier, the application installs normally.

+62
Apr 25 '11 at 17:33
source share
β€” -

The problem for me was that my download plist file had a different package identifier than my bundleID agent. Fixing the boot plist file worked.

Alternatively, rebooting also worked, but it was a big pain every time.

+10
Jun 28 '11 at 6:13
source share

I used the package identifier - com.myname. {appId} in the application info.list file. But in my OTA manifest file, I used com.myname. * Due to this problem, my installation fails. I changed both places com.myname.APPName, then it works as smart.

+4
Jul 26 '11 at 7:24 a.m.
source share

**

I had exactly the same problem and it was solved by following these steps.

**

Description of the problem To clarify, the problem (the application does not install properly - the icon disappears after installation) occurs only on the iOS device (the Android version of the same application assembly works fine).

Source of the problem In my case, the problem was due to the fact that the test iPad device that I used was not registered (added) to the Provisioning Profile used by my application.

Learning This means that the iOS developer application cannot be installed on any given test device until it is added to the Provisioning Profile (PP). Important information also is that after the device is added to the PP, you need to create a new PP, and the application must be signed using this new PP to complete the handshake.

Repair steps

  • Sign in to Apple Developer https://developer.apple.com
  • Go to "Certificates, Identifiers, and Profiles" β†’ "Devices"
  • After checking that the device is not in the list, click "+", enter image description here
  • Fill in the "Name" and "UDID" of your test device and click "Continue." enter image description here
  • After the device is added to the list, create a new PP by clicking on the link "Provisioning Profiles" β†’ "Development" β†’ Click on an existing PP β†’ "Edit" β†’ check the new device in the "Devices" section β†’ click "Create" β†’ "Download "β†’" Finish " enter image description here
  • Use the new downloaded PP to sign a new development application.
  • Install a new application on a test device
  • Celebrate success
+2
Oct 06 '17 at 3:45
source share

Is the device OS version below the deployment level of the target application platform?

If so, omit the application deployment target in the Ad Hoc Build for Target settings or update the device OS.

+1
Apr 09 2018-11-18T00:
source share

If anyone else has this problem, make sure you register the device you are testing on, and that device is also registered under the condition that you use

0
Aug 16 '16 at 9:46 on
source share



All Articles