• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Can't debug on devices
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Can't debug on devices


  • Subject: Re: Can't debug on devices
  • From: Doug Hill <email@hidden>
  • Date: Tue, 26 May 2015 14:20:41 -0700

Luther, thanks for the info. As before, still no devices in the Destinations menu.

After doing some more investigation, I found the following in the System console:

kernel[0]: proc 7172: load code signature error 4 for file "Xcode"

amfid[96]: /Applications/Xcode.app/Contents/MacOS/Xcode signature not valid: 0xfffefa31

taskgated[97]: killed com.apple.dt.Xcode[pid 7172] because its use of the com.apple.developer.maps entitlement is not allowed (error code -67063)

com.apple.xpc.launchd[1]: (com.apple.dt.Xcode.52856[7172]) Service exited due to signal: Killed: 9

FWIW, the only way I could get this working again was to re-download Xcode and CLTs from ADC and install again.

Doug Hill
http://chartcube.com/


On May 26, 2015, at 1:28 PM, Luther Baker <email@hidden> wrote:

Doug,

Had the same problem (I think?) when I upgraded to 6.3.1.

Workaround for me was to use a different menu to select the device:
  1. Click on "Product" menu
  2. Click on "Destination" submenu
  3. Find your device listed ... oddly selectable
The problem went away by itself after a few days and now I can select my devices from the main view drop down.

Good luck,
-Luther



On Tue, May 26, 2015 at 1:45 PM, Doug Hill <email@hidden> wrote:
I just upgraded Xcode to the latest 6.3.2 (6D2105).

Now I can’t debug on any devices. I tried two different phones (an iPhone 5S and iPhone 6+) with two different cables but they never show up in the device menu when trying to Run. The device does show up in the Devices window and I don’t see anything unusual there (e.g. loading symbols).

In the Console log I see the following messages when plugging in a device:

5/22/15 1:13:34.338 PM iTunes[575]: Entered:_AMMuxedVersion2DeviceConnected, mux-device:18
5/22/15 1:13:34.348 PM iTunes[575]: tid:1bef - unable to query device capabilities
5/22/15 1:13:35.706 PM com.apple.usbmuxd[76]: MuxTCPInputSCE received RST for 0x12-e5f6398b1f473792179cdb571e6867d0e28d1814@0x14110000:49600->0x100504c40-Xcode/com.apple.dt.Xcode:33026: sendMuxSegment connection was closed

Checking in the App Store app for recent updates, I see two different listings for Command Line tools, which looks weird. Both version of Command Line tools are shown as Version 6.3 but the Xcode version that was installed is 6.3.2.

FWIW, I installed from the command-line tools downloaded off of ADC but with no effect.

Anyways, if anyone has any ideas on how to get my devices back, please let me know.

Doug Hill
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Can't debug on devices (From: Doug Hill <email@hidden>)
 >Re: Can't debug on devices (From: Luther Baker <email@hidden>)

  • Prev by Date: Re: Can't debug on devices
  • Next by Date: is it possible to determine from a static archive file on disk which c++ compiler/linker flags were used to build it?
  • Previous by thread: Re: Can't debug on devices
  • Next by thread: is it possible to determine from a static archive file on disk which c++ compiler/linker flags were used to build it?
  • Index(es):
    • Date
    • Thread