Best IT Recipes

An unknown error occurred when I tried to use the iPad for development.

I tried to test my application on the new iPad to see if Retina support works.

Like all the other devices that I used for development, I connected the device and clicked "Use for development" - this is Xcode Organizer.

The process started, but after a few seconds the progress indicator disappeared, and I received this error message: "An unknown error occurred"

I manually registered my UDID section in devices, and the provisioning profile was successfully installed on the device, but there is still a yellow dot in front of the iPad name in the organizer, and the device does not appear in the list of iOS devices (so I cannot launch my application on it).

I tried something that occurred to me, but nothing worked :(

enter image description here

Any ideas?



Additional Information:

  • Xcode Version: 4.4.1
  • IOS SDK Version: 5.1
  • Minimum Deployment Goal: 5.0
  • IOS device version: 5.1.1 (9B206)
  • Device Type: 3rd Gen New iPad (Wifi + 4G)
  • Intel Mac: Mac Pro with 2 x 2.26 GHz dual-core Intel xeon processor
  • OS Version: OS X Mountain Lion 10.8 (12A269)
+46
ios xcode provisioning-profile deployment-target
Sep 18 '12 at 20:50
source share
13 answers

Try disconnecting / reconnecting the iPad, logging out and restarting Xcode, ... Sometimes it just won't work, and restarting solves everything!

+135
Sep 18 '12 at 22:20
source share

This happened to me a lot when I am connected via an Apple USB keyboard (which has two USB ports at the bottom).

If you connect several keys on this keyboard, for example, two iPhones, it will not be able to deliver enough power for both, and you will begin to receive intermittent disconnections.

Solution: Connect directly to the Mac.

+10
May 08 '14 at 1:47
source share

Once it happened to me, and it seemed that my iCloud account on my device was not registered. This was due to the password change I made. After I returned with the proper password, the application seemed to fit perfectly into the device. :-)

+7
Oct 08 '15 at 14:18
source share

In my case, having tried everything (restarting iPad, Xcode, imac), I found out that the problem was caused by the same application that still works on the background of the iPad from the previous launch. I just had to reject the application from the iPad, and everything was fixed.

+4
Nov 18 '16 at 21:03
source share

Not a duplicate, but OS X, Xcode and IOS often fall on their swords due to code failure and caching, see if something helps here: Error: Could not start when working on ipad

+2
Oct 08 '15 at 15:01
source share

I was able to fix this problem by changing the signature identifier from one team to another, and then reverted to the original command.

+1
Feb 29 '16 at 18:24
source share

You can use xcode-> windows-> devices and look at the device log to get more information about the "Unknown error", you will get something like this:

  • 0x16e12f000 + [MICodeSigningVerifier _validateSignatureAndCopyInfoForURL: withOptions: error:]: 142: Failed to verify code signature / private / var / mobile / Library / Caches / com.apple.mobile.installd.staging / temp.L5Dvt0 / extracted / Payload / Xxx .app / PlugIns / packetTunnel.appex: 0xe8008001 (An unknown error has occurred.)

I saw "Unknown error" under the following conditions and correct it by correcting the code:

  • I write @interface with a class and forget @implementation with that class name in the extension target.
  • There is no code in one object of my project.
+1
Jul 29 '16 at 5:13
source share

I got this error when trying to install a 1 GB application on a device with a balance of 300 MB. I did not expect this to be a problem, since the application was already installed on the device from iTunes, and I just installed a local assembly to overwrite it, but I repeatedly received this error until I deleted the copy from the store. After that, it worked fine.

0
May 13 '15 at 18:12
source share

I could get this to work by plugging in my phone again, and then launching iCloud welcome screens on my laptop.

0
Jun 27 '16 at 8:38
source share

I found that due to the fact that my iphone was gone and I was charging it, first I had to open the phone with a pin so that Xcode could connect to

0
Jul 09 '16 at 23:33
source share

I had the same error message when I installed new containers (CocoaPods). I was able to fix this problem by removing the last added modules from my project.

0
Jul 17 '16 at 19:47
source share

It happened to me when iTunes was open in the background. Closing iTunes and Xcode and then reopening Xcode worked for me.

0
Sep 20 '16 at 15:05
source share

I regularly encounter the same problems: restarting the iPhone fixes this every time

0
Jun 26 '19 at 9:01
source share


More articles:


All Articles