Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: XE7 - iOS Device - Debug - "unable to install package. (e800003a)."


This question is answered. Helpful answers available: 2. Correct answers available: 1.


Permlink Replies: 2 - Last Post: Feb 16, 2015 4:38 AM Last Post By: Andrew Law
Andrew Law

Posts: 74
Registered: 11/6/02
XE7 - iOS Device - Debug - "unable to install package. (e800003a)."  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 13, 2015 5:52 AM
Hi,

I'm trying to run a reasonably simple app on a new iOS device, attached to my pre-existing Mac, using C++ XE7.

The app compiles and links just fine, and appears to deploy fine, at least as far as the Mac (.e.g. Project -> Deploy completes with no errors). But after "launching..." appears on the Run dialog, I get the error mentioned in the summary after less than one second.

This error value is not listed in the XE7 "Troubleshooting: Cannot Deploy to the iOS Device" help page.

There's no additional info that I can see on the PAServer console, after enabling verbose mode, either, other than "iOS output: err=Unable to install package. (e800003a). - suggesting that it is the iOS device that won't accept the app.

Does anyone have any experience with resolving this particular error code, or what it represents?

Thanks,
Andrew
Antonio Estevez

Posts: 665
Registered: 4/12/00
Re: XE7 - iOS Device - Debug - "unable to install package. (e800003a)."  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 13, 2015 6:50 AM   in response to: Andrew Law in response to: Andrew Law
El 13/02/2015 a las 14:52, Andrew Law escribió:
Hi,

I'm trying to run a reasonably simple app on a new iOS device, attached to my pre-existing Mac, using C++ XE7.

The app compiles and links just fine, and appears to deploy fine, at least as far as the Mac (.e.g. Project -> Deploy completes with no errors). But after "launching..." appears on the Run dialog, I get the error mentioned in the summary after less than one second.

This error value is not listed in the XE7 "Troubleshooting: Cannot Deploy to the iOS Device" help page.

There's no additional info that I can see on the PAServer console, after enabling verbose mode, either, other than "iOS output: err=Unable to install package. (e800003a). - suggesting that it is the iOS device that won't accept the app.

Does anyone have any experience with resolving this particular error code, or what it represents?

Thanks,
Andrew

Try this:

http://blogs.embarcadero.com/sarinadupont/2015/01/29/ios-813-app-deployment-steps-for-xe7/
Andrew Law

Posts: 74
Registered: 11/6/02
Re: XE7 - iOS Device - Debug - "unable to install package. (e800003a)."  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 16, 2015 4:36 AM   in response to: Antonio Estevez in response to: Antonio Estevez
Antonio Estevez wrote:


Wow, thanks for that. After several hours of studying this, and the XE7 documentation, and the Apple documentation to try to understand what was really meant by some of the steps (no worked examples), I have got around this issue.

For anyone else who's struggling with this, may I relate my experience on getting past this:

1) Options A and B in Sarina's article did not help me. Next time I will proceed directly to option C.
2) I couldn't find the provisioning profile file using Finder - Terminal was required in order to be able to see the "MobileDevice" folder. Then I could copy the generated txt file to a folder that was visible to Finder (e.g. Desktop).
3) The somewhat cryptic discussion about replacing one or more of the asterisk characters with part of your profile ID should best be interpreted as replacing only the first asterisk character (the one inside the <array> tag) and not the second one.
4) Finally, read the "small print" at the very top, and delete the <Project>.entitlements file before building, otherwise you may get e8008016, which is another code number not mentioned in the documentation.

Is provisioning for iOS always this hard? Or is this due to something about iOS 8.1.3, and if so, at what stage will provisioning no longer require all these steps?

Thanks again,
Andrew
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02