20

Running any XCTest with Xcode 11 and iOS 13/12 simulators throws the below warning message:

xcodebuild[95489:2342933] [MT] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/DVTiOSFrameworks/DVTiOSFrameworks-14802/IDEiOSSupportCore/DVTiPhoneSimulator.m:1890

Details: [DVTiPhoneSimulator -primaryInstrumentsServer was called from the main thread

Object:

Method: -primaryInstrumentsServerWithError:

Thread: {number = 1, name = main}

Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.

This issue happens a lot when running tests in parallel (or a single test) using xcodebuild build-for-testing & xcodebuild test-without-building. Has anyone encountered this issue and found a fix for it?

shim
  • 9,289
  • 12
  • 69
  • 108
mark w.
  • 1,047
  • 9
  • 16
  • Looks like bug in the iOS support code for iPhone Simulator, specifically actions are not happening on the correct thread (probably should be called as a background task.) I would file a radar.. Does unchecking the run tests in parallel option make the problem go away? – ablarg Sep 23 '19 at 20:57
  • I am not running the tests in parallel via XCode, instead running them via xcodebuild from the terminal – mark w. Sep 30 '19 at 15:50
  • I'm seeing this issue in my own tests, pretty clearly appears to be an Apple issue. – ablarg Sep 30 '19 at 22:21
  • Same here, the only tests which succeed are the ones on the "iPad Pro (12.9-inch)" simulator..no idea why – Gerald Eersteling Oct 14 '19 at 08:02
  • @markw. Facing the same issue, did you find any solution for this? – Samarth Kejriwal Nov 01 '19 at 05:53
  • nothing yet. I even logged an issue with Apple - https://forums.developer.apple.com/thread/123020. Please feel free to raise your concerns there as well so that Apple knows it's affecting everyone. – mark w. Nov 04 '19 at 21:08

2 Answers2

2

Link to source for answer https://forums.developer.apple.com/thread/123020#392637 it seems it would be solved on iOS 13.2

Juan Carlos Ospina Gonzalez
  • 4,153
  • 3
  • 34
  • 43
1

Apple finally fixed this on iOS 13.2, so sharpen your downloading knives :)

mark w.
  • 1,047
  • 9
  • 16