Iphone – adhoc app installation failed in iPhone , why

adhocinstallationiphone

I am developing an iPhone application .

As the application is location aware I am testing it on a different (where I am not present).

For that I am sending my friend a .mobileprovision profile and the application adhoc build.

But At his end the application installation stops in between .

In the device log it gives me the following log :

2:42:30 unknown mobile_installationd[164] <Error>: 00808800 install_embedded_profile: Skipping the installation of the embedded profile
Wed Nov 11 12:42:31 unknown mobile_installationd[164] <Error>: 00808800 verify_executable: Could not validate signature: e8008017
Wed Nov 11 12:42:31 unknown mobile_installationd[164] <Error>: 00808800 preflight_application_install: Could not verify /var/tmp/install_staging.HreENJ/foo_extracted/Payload/RestaurantApp .app/RestaurantApp
Wed Nov 11 12:42:31 unknown mobile_installationd[164] <Error>: 00808800 install_application: Could not preflight application install
Wed Nov 11 12:42:31 unknown mobile_installation_proxy[163] <Error>: handle_install: Installation failed
Wed Nov 11 12:42:31 unknown mobile_installationd[164] <Error>: 00808800 handle_install: API failed
Wed Nov 11 12:42:31 unknown mobile_installationd[164] <Error>: 00808800 send_message: failed to send mach message of 64 bytes: 10000003
Wed Nov 11 12:42:31 unknown mobile_installationd[164] <Error>: 00808800 send_error: Could not send error response to client

So can anyone tell me what this error says so the installation fails ?

I found this is a very common and frustrating problem . And not even one has a perfect solution.

The apple technical note :http://developer.apple.com/iphone/library/technotes/tn2009/tn2242.html

Best Answer

Looks as though your provisioning profile is duff in some way. Here's now I normally work around the problem:

Delete your whole build folder. Clean All should do this for you but does seem to leave bits behind from time to time
Check the device ID in the Developer Center. Edit it if you need to.
Download the profile again.
Install the profile again.
Quit Xcode and reload.
Make sure you've set Xcode to use the new, ad hoc profile rather than your developer profile, for the Code Signing Identity of the configuration you will be using for the archive.
Build
Take a copy of the executable straight away

It would be neat if there was some way of finding which step went wrong, but until that happens it's usually best just to start from scratch unless you have very patient (or local) testers.

Related Solutions

Ios – How to develop for iPhone using a Windows development machine

It's certainly possible to develop on a Windows machine, in fact, my first application was exclusively developed on the old Dell Precision I had at the time :)

There are three routes;

Install OSx86 (aka iATKOS / Kalyway) on a second partition/disk and dual boot.
Run Mac OS X Server under VMWare (Mac OS X 10.7 (Lion) onwards, read the update below).
Use Delphi XE4 and the macincloud service. This is a commercial toolset, but the component and lib support is growing.

The first route requires modifying (or using a pre-modified) image of Leopard that can be installed on a regular PC. This is not as hard as you would think, although your success/effort ratio will depend upon how closely the hardware in your PC matches that in Mac hardware - e.g. if you're running a Core 2 Duo on an Intel Motherboard, with an NVidia graphics card you are laughing. If you're running an AMD machine or something without SSE3 it gets a little more involved.

If you purchase (or already own) a version of Leopard then this is a gray area since the Leopard EULA states you may only run it on an "Apple Labeled" machine. As many point out if you stick an Apple sticker on your PC you're probably covered.

The second option is more costly. The EULA for the workstation version of Leopard prevents it from being run under emulation and as a result, there's no support in VMWare for this. Leopard server, however, CAN be run under emulation and can be used for desktop purposes. Leopard server and VMWare are expensive, however.

If you're interested in option 1) I would suggest starting at Insanelymac and reading the OSx86 sections.

I do think you should consider whether the time you will invest is going to be worth the money you will save though. It was for me because I enjoy tinkering with this type of stuff and I started during the early iPhone betas, months before their App Store became available.

Alternatively, you could pick up a low-spec Mac Mini from eBay. You don't need much horsepower to run the SDK and you can always sell it on later if you decide to stop development or buy a better Mac.

Update: You cannot create a Mac OS X Client virtual machine for OS X 10.6 and earlier. Apple does not allow these Client OSes to be virtualized. With Mac OS X 10.7 (Lion) onwards, Apple has changed its licensing agreement in regards to virtualization. Source: VMWare KnowledgeBase

R – How to properly develop for the iPhone on a PowerPC Mac

I had the same problems as you - I could cross compile and install the app on the iphone, but it would always fail with a security violation.

To get around it, I had to jailbreak my phone and install a patched MobileInstaller (I believe the Cydia app now has package called Installous which patches your MobileInstaller. Unfortunately, I think Installous is also used to pirate apps). Then in your project's Info.plist, you need to add the following:

<key>SignerIdentity</key>
<string>Apple iPhone OS Application Signing</string>

This will allow your phone to run unsigned binaries, which is the only way I was able to develop from my ppc mac.

I'm still able to purchase apps from the appstore and have them run without any problems.

Best Answer

Related Solutions

Ios – How to develop for iPhone using a Windows development machine

R – How to properly develop for the iPhone on a PowerPC Mac

Related Topic