Please advcie how to resolve this?

Anyway, following the instructions apbove solved the problem although I had two attempts on which “John Davies” to use as your example shows both lines being the same. (I know it’s obvious but when you’ve spent hours trying to get this working you’re ready to try anything and everything.). It’s the one on the certificate line “iPhone Developer: John Davies” in my case.

Finally I’d like to post the reply from Apple that helped me finally get through the “Error 0xE800003A” horror, I’d been working fine on one machine and knew nothing of the horrors of certificates and signing until I tried to put my app onto a second beta tester, I lost days trying to solve it.

—- A reply from Apple (after 1 default response and 2 other emails) —-

Hello John,

The primary issue is reflected by this line in the error log:

Wed May 13 12:09:35 unknown mobile_installation_proxy[1101] :
entitlement ‘get-task-allow’ has value not permitted by a provisioning

You mentioned that you’re doing an Ad Hoc build, and that you’d started to create an Entitlements.plist but didn’t complete it. This would be the issue. In order for an Ad Hoc build to run on a device, you have to have the get-task-allow Entitlement turned off. This is described in the Ad Hoc Distribution section of the iPhone Portal.

In short, create an Entitlements.plist file (File > New File > Code Signing), uncheck the “get-task-allow” checkbox, and enter the name of the file in your Target’s Code Signing Entitlements section.

The second issue is that you have two code signing identities selected for your Project and Target. You have “iPhone Developer: John Davies” on the first line, and “iPhone Distribution: John Davies” on the second line.

Putting aside the inherent conflict of two different code sign identities, there’s also the issue that you should only have one entry, on the Any iPhone OS Device line. Delete the entry on the Code Signing Identity line. Make sure you do this for both your Project and your Target Info windows.

Be sure to do a clean build after making these changes (it might be worthwhile to delete your entire build folder manually).

—- Finally after my thank you —-

I’m glad things are resolved. Xcode can be aggressive with its caching on occasion. I find that these items, done in order of escalation, work to clear out any overly persistent data:

* Clean builds (Build > Clean all Targets)
* Deleting the build folders manually
* Selecting Xcode > Empty Caches…
* Restarting Xcode
* Restarting your Mac

(I haven’t seen an issue that goes past restarting Xcode, but I figured I’d toss it in for completeness.)

—- I’d like to thank the Ralf for the posting above and the guy at Apple who helped me, I’ve left his name off as I’ve not asked permission to post it, I hope they don’t mind.

Good luck everyone,

-John-

Thanks

*** For others:
if you encounter AppVerifificationFailed or other 0x00xxxxx errors, do “Build–>Clean All Targets” in XCode before building it again. This simple fix will save you lot of debugging hours.
***

A bit of the instructions was slightly not in sync with what I had, but those items seemed to be not important. I finally ran my first iPhone app on the actual device, not just the simulator…

Thanks!