Simulator not working in Xcode 7.3

After updating to Xcode 7.3, My app is not launching in simulator. It shows error which is show in attached image. I've restarted Xcode, Simulator and my Mac mini but nothing happen. App is installed in simulator but after that it shows this error :

"DTAssetProviderService could not start DTXConnection with simulator 'iPhone 5s". Check the system log for errors."


Steps to Reproduce:

  1. Build
  2. Run
  3. Simulator launch
  4. App is installed in Simulator
  5. Error shows


Version: Xcode Version : 7.3

Mac OS : 10.11.3

iOS : 9.3


It is working completely fine in Xcode 7.2.1 with iOS 9.2

Replies

I don't see an attached image.


I've also seen a report of this on stackoverflow.com (http://stackoverflow.com/questions/36200318/dtassetproviderservice-could-not-start-dtxconnection-with-simulator and http://stackoverflow.com/questions/36244082/dtassetproviderservice-could-not-start), but so far nobody has provided the relevant details to diagnose the problem. The error message states, "Check the system log for errors." so could you please provide the relevant errors from the system log?

Hi,

I am having the same issue. I've tried rebooting, using different simulators (iPhone 5, 6, etc) and still getting this error message. The simulator launches, and I can then "launch" the app from the simulator itself by clicking on it, but at this point it is not connected to Xcode. As in, when I launch the app, I don't see what is getting returned to the console via print statements, etc.


I'm attached the log here. I hope you can help me solve this problem, as it has been very frusterating.


ps...I'm trying to post a screen shot of the log, but can't seem to find how to do this...sorry


edit:


here is the text of the log:

Mar 24 10:18:38 CoreSimulatorService[521] : com.apple.CoreSimulator.CoreSimulatorService 209.19 starting.

Mar 24 10:18:44 CoreSimulatorService[521] : Requested watch is is not available for pairing. Assuming it has the capability.

Mar 24 10:18:44 CoreSimulatorService[521] : Requested phone is is not available for pairing. Assuming it has the capability.

Mar 24 10:18:44 CoreSimulatorService[521] : Requested watch is is not available for pairing. Assuming it has the capability.

Mar 24 10:18:44 CoreSimulatorService[521] : Requested phone is is not available for pairing. Assuming it has the capability.

Mar 24 10:18:45 com.apple.dt.Xcode[455] : Requested watch is is not available for pairing. Assuming it has the capability.

Mar 24 10:18:45 com.apple.dt.Xcode[455] : Requested phone is is not available for pairing. Assuming it has the capability.

Mar 24 10:18:45 com.apple.dt.Xcode[455] : Requested watch is is not available for pairing. Assuming it has the capability.

Mar 24 10:18:45 com.apple.dt.Xcode[455] : Requested phone is is not available for pairing. Assuming it has the capability.

Mar 24 11:02:29 com.apple.iphonesimulator[712] : Requested watch is is not available for pairing. Assuming it has the capability.

Mar 24 11:02:29 com.apple.iphonesimulator[712] : Requested phone is is not available for pairing. Assuming it has the capability.

Mar 24 11:02:29 com.apple.iphonesimulator[712] : Requested watch is is not available for pairing. Assuming it has the capability.

Mar 24 11:02:29 com.apple.iphonesimulator[712] : Requested phone is is not available for pairing. Assuming it has the capability.

Mar 24 11:02:31 CoreSimulatorService[521] : Could not register service com.apple.coreservices.lsuseractivity.simulatorsupport: Failed to lookup com.apple.coreservices.lsuseractivity.simulatorsupport: 0x44e

Unfortunately, all of those log lines are expected. Do you see anything from Xcode in /var/log/system.log.


Any advice you can give on reproducing?


What is your hardware configuration? HDD? Some have reported that the issue goes away on subsequent launches with the same device which makes me suspect that boot is just taking a long time and triggering a timeout in Xcode.

I have the same problem too, same logs also.


I had to switch back to an old computer without SSD :


- Mac Mini late 2011

- Core i5 2.5 Ghz

- 8 Go RAM 1333


Prior to that had a Core i7 + 16 Go RAM + SSD, it was working fine.

Hi Jeremy. I've been running into this issue myself, I've been trying to get automated UI tests working on the simulator in a CI environment (jenkins)

I'm going to throw a bunch of logs at you, as well as the script that i'm using to invoke everything. Please let me know if i can provide any other info, i'm happy to help.

edit: I should mention that these failures are intermittent, you may need to run a few times to reproduce.

i'm using the XCode 7.3.1 GM from a few days ago, and ive got a couple brand new mac minis. they are connected to jenkins via JNLP.

also, googling for "DTXProxyChannel" shows a few people may be experiencing this error with Travis CI as well


==BASH SCRIPT THAT KICKS OFF UI TESTS

killSimResult=`killall Simulator`
echo attempted to kill simulator with result $killSimResult
#these variables are expected to be provided by the containing jenkins job
#we're providng some default values so that we can run these tests outside jenkins
name=${JOB_NAME:-default_job_name}
build=${BUILD_DISPLAY_NAME:-default_build_str}
simName=$name$build

simRuntime=${SIMULATOR_RUNTIME:-com.apple.CoreSimulator.SimRuntime.iOS-9-3}
iosDevice=${IOS_DEVICE_TYPE:-com.apple.CoreSimulator.SimDeviceType.iPhone-6}

echo will attempt to create simulator with name $simName
#Usage:       simctl create <name> <device type id> <runtime id>
SIM_ID=`xcrun simctl create ${simName} ${iosDevice} ${simRuntime}`
echo created simulator with ID $SIM_ID
pod update;
sleep 2
echo invoking xcodebuild...
xcodebuild -workspace slideshow.xcworkspace -scheme slideshowUITesting -destination id=$SIM_ID ONLY_ACTIVE_ARCH=YES clean test | xcpretty --test --report junit --report html && exit ${PIPESTATUS[0]}
sleep 10
echo finished test process
xcrun simctl shutdown $SIM_ID;
sleep 2
xcrun simctl delete $SIM_ID;
sleep 2

==JENKINS BUILD LOG
invoking xcodebuild...
2016-04-26 16:31:18.924 xcodebuild[70136:340555] [MT] IDETestOperationsObserverDebug: (17822D3E-CC16-4903-8686-51D7777B2F03) Beginning test session 17822D3E-CC16-4903-8686-51D7777B2F03 with Xcode 7D1012 on target <DVTiPhoneSimulator: 0x7fe2bb72d130> {
  SimDevice: SimDevice : Run_XCSmoke_Tests_for_iOS_Universal_App_on_iPhone_Simulator#228 (635A7BE4-7EFC-484D-B9CA-084B4DAC9878) : state={ Shutdown } deviceType={ SimDeviceType : com.apple.CoreSimulator.SimDeviceType.iPhone-6 } runtime={ SimRuntime : 9.3 (13E230) - com.apple.CoreSimulator.SimRuntime.iOS-9-3 }
} (9.3 (13E230))
2016-04-26 16:31:18.925 xcodebuild[70136:340620]  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
/Users/jenkins/Library/Developer/Xcode/DerivedData/slideshow-fshocqmtceesaagvwdjjkvddjccx/Logs/Test/E49709C6-156A-46FD-96FA-8B6FFC223C43/Session-2016-04-26_16:31:18-oV06qP.log

==XCTRUNNER LOG  (the log file referenced above ^)
16:31:19.974 xcodebuild[70136:340558] Connected to testmanagerd socket for Sim Run_XCSmoke_Tests_for_iOS_Universal_App_on_iPhone_Simulator#228
16:31:19.975 xcodebuild[70136:340558] Creating the connection.
16:31:19.976 xcodebuild[70136:340558] Listening for proxy connection request from the test bundle (all platforms)
16:31:19.976 xcodebuild[70136:340558] Resuming the connection.
16:31:19.977 xcodebuild[70136:340558] Test connection requires daemon assistance.
16:31:19.977 xcodebuild[70136:340555] Checking test manager availability..., will wait up to 120s
16:31:19.979 xcodebuild[70136:340555] Starting test session with ID <__NSConcreteUUID 0x7fe2bed425c0> 17822D3E-CC16-4903-8686-51D7777B2F03
16:31:46.480 xcodebuild[70136:340612] Error from testmanagerd: The operation couldn’t be completed. (DTXProxyChannel error 1.) ((null))
16:31:46.480 xcodebuild[70136:340555] Test operation failure: The operation couldn’t be completed. (DTXProxyChannel error 1.)
16:31:46.480 xcodebuild[70136:340555] _finishWithError:Error Domain=IDETestOperationsObserverErrorDomain Code=3 "The operation couldn’t be completed. (DTXProxyChannel error 1.)" UserInfo={NSLocalizedDescription=The operation couldn’t be completed. (DTXProxyChannel error 1.)} didCancel: 1

==OSX CONSOLE LOG (note the timestamps)
4/26/16 4:30:33.624 PM com.apple.CoreSimulator.CoreSimulatorService[613]: Requested watch is is not available for pairing.  Assuming it has the capability.
4/26/16 4:30:33.624 PM com.apple.CoreSimulator.CoreSimulatorService[613]: Requested watch is is not available for pairing.  Assuming it has the capability.
4/26/16 4:30:33.625 PM com.apple.CoreSimulator.CoreSimulatorService[613]: Requested watch is is not available for pairing.  Assuming it has the capability.
4/26/16 4:31:01.810 PM mds[60]: (DiskStore.Normal:2382) 4001 1.011318
4/26/16 4:31:15.227 PM com.apple.usbmuxd[69926]: LOCKDOWN_V2_BONJOUR_SERVICE_NAME is _apple-mobdev2._tcp,901d07e3
4/26/16 4:31:15.296 PM com.apple.CoreSimulator.CoreSimulatorService[613]: Requested watch is is not available for pairing.  Assuming it has the capability.
4/26/16 4:31:15.296 PM com.apple.CoreSimulator.CoreSimulatorService[613]: Requested watch is is not available for pairing.  Assuming it has the capability.
4/26/16 4:31:15.296 PM com.apple.CoreSimulator.CoreSimulatorService[613]: Requested watch is is not available for pairing.  Assuming it has the capability.
4/26/16 4:31:18.925 PM xcodebuild[70136]: [MT] IDETestOperationsObserverDebug: (17822D3E-CC16-4903-8686-51D7777B2F03) Beginning test session 17822D3E-CC16-4903-8686-51D7777B2F03 with Xcode 7D1012 on target <DVTiPhoneSimulator: 0x7fe2bb72d130> {
SimDevice: SimDevice : Run_XCSmoke_Tests_for_iOS_Universal_App_on_iPhone_Simulator#228 (635A7BE4-7EFC-484D-B9CA-084B4DAC9878) : state={ Shutdown } deviceType={ SimDeviceType : com.apple.CoreSimulator.SimDeviceType.iPhone-6 } runtime={ SimRuntime : 9.3 (13E230) - com.apple.CoreSimulator.SimRuntime.iOS-9-3 }
} (9.3 (13E230))
4/26/16 4:31:18.926 PM xcodebuild[70136]:  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
/Users/jenkins/Library/Developer/Xcode/DerivedData/slideshow-fshocqmtceesaagvwdjjkvddjccx/Logs/Test/E49709C6-156A-46FD-96FA-8B6FFC223C43/Session-2016-04-26_16:31:18-oV06qP.log
4/26/16 4:31:19.095 PM com.apple.CoreSimulator.CoreSimulatorService[613]: Requested watch is is not available for pairing.  Assuming it has the capability.
4/26/16 4:31:19.095 PM com.apple.CoreSimulator.CoreSimulatorService[613]: Requested watch is is not available for pairing.  Assuming it has the capability.
4/26/16 4:31:19.095 PM com.apple.CoreSimulator.CoreSimulatorService[613]: Requested watch is is not available for pairing.  Assuming it has the capability.
4/26/16 4:31:19.902 PM com.apple.CoreSimulator.CoreSimulatorService[613]: Could not register service com.apple.coreservices.lsuseractivity.simulatorsupport: Failed to lookup com.apple.coreservices.lsuseractivity.simulatorsupport: 0x44e

That seems to be a different error message than the one being discussed here, "DTAssetProviderService could not start DTXConnection"

I don't see any open radars about that "DTXProxyChannel error 1" so please file one at http://bugreport.apple.com. Include that data above, ~/Library/Logs/CoreSimulator, and a sysdiagnose taken while the issue is reproducing.

I also have same issue. Might anyone have any update? Thanks


I'm running OSX 10.11.5 (15F34) and xcode 7.3.1 (7D1014) on MacBook Pro (13-inch, Early 2011).


Errmsg "DTAssetProviderService could not start DTXConnection with Simulator 'iPhone 6 Plus'. Check the system log for errors." shows up every time simulator is launched by clicking "play" button on xcode

When you say every time, does that include immediately after rebooting your mac and trying again? Did you reset the simulator?


How much free space on your MBP?


All other simulators work ok?


How many times have you reinstalled Xcode? From the MAS or dev downloads?

I have the same issue with Xcode 7.3. This is the output of the system log. I guess the last line can give a hint.


Jun 14 08:51:51 Lucass-MacBook-Pro installd[3442]: 0x70000e678000 -[MIInstaller performInstallationWithError:]: Install Successful; Staging: 0.03s; Waiting: 0.00s; Preflight/Patch: 0.18s, Verifying: 0.00s; Overall: 0.25s

Jun 14 08:51:51 Lucass-MacBook-Pro pkd[3481]: releasing plug-in hold 3D79C100-C2D2-4BFB-BDCC-84A39BBF5ACB at client's request

Jun 14 08:51:51 Lucass-MacBook-Pro SpringBoard[3448]: Installed apps did change.

Added: {(

)}

Removed: {(

)}

Modified: {(

"....."

)}

Jun 14 08:51:52 Lucass-MacBook-Pro containermanagerd[3465]: 0x70000774c000 systemGroupContainerPath: com.apple.containermanagerd.internal is not entitled for system group identifier: systemgroup.com.apple.***

Jun 14 08:51:52 Lucass-MacBook-Pro ***[3507]: LaunchServices:(called by PID 3456) Identifiers file does not exist, creating file.

Jun 14 08:51:52 Lucass-MacBook-Pro containermanagerd[3465]: 0x7000076c9000 systemGroupContainerPath: com.apple.containermanagerd.internal is not entitled for system group identifier: systemgroup.com.apple.***

Also found this in the system log:

Jun 14 14:37:58 Lucass-MacBook-Pro Xcode[7747]: +[DTServiceHubClient localConnectionWithAuthorization:returningServerPid:]: failed to establish connection with DTServiceHub service '/Applications/Xcode.app/Contents/SharedFrameworks/DVTInstrumentsFoundation.framework/Resources/DTServiceHub'

I fixed this by updating to Xcode 8 beta.

Please note that those of you seeing this mssage when trying to run Xcode 7.3 on Sierra are most likely not seeing the same bug as being discussed in this thread. There are two issues here that can have the same symptom/dialog:


1) Xcode 7.3 on Xcode 8 Beta running on older hardware, I/O bottlenecked systems, etc.

2) AppStore-downloaded Xcode 7.3 running on Sierra.


For #1, the workaround is to boot the simulator first before doing the Build & Run.

For #2, the only workarounds are to either not use Build&Run or to instead get Xcode 7.3 from http://downloads.apple.com

I have the same issue. With both betas on my MackBookPro, and iMac, the simulator launch faiure begins either on installation or soon after.. But once error starts the simulator will no longer execute.


Update: I reinstalled the betas on my iMac. the simulator is working. On my MacBookPro. I just rebooted my computer and the simulator works, with xCode 8. I think when attempting to run the simmulator fron xCode 7, MacOS doesn't like that.

Hi Jeremy


I cannot get the simulator working in Xcode 7 after installing Xcode 8 beta. Could you please assist? What info do you need from me? I have trierd what is suggested in this thread, but no luck.

Please start a new thread with more specific details.