Xcode 3.2 in Snow Leopard hangs on unit test tests

So, I have some unit tests that pass in Xcode 3.1 / Leopard. They use SenTestingKit in the iPhone application project and are created / run in a separate target program. I just upgraded to Xcode 3.2 on Snow Leopard and the tests seem to run (I get the logs in Console.app and see their transfer), but Xbox kayaks should be forced to close after they run. Console.app displays the following error from Xcode that appears even if test cases are not included in the test target:

Xcode[1734] -[XCBuildLogCommandInvocationSection setTestsPassedString:]: unrecognized selector sent to instance 0x20104db60 Xcode[1734] -runOperationInBackground raised an exception: -[XCBuildLogCommandInvocationSection setTestsPassedString:]: unrecognized selector sent to instance 0x20104db60 

I cleaned and redid it to no avail, and I cannot find anything on this topic by doing a search (although it looks like one person has the same problem).

Update: I reported this as an error for Apple with error # 7214051.

+4
source share
6 answers

I also posted an error report for this, 7210948. There is still no Apple response that is discouraging.

-

Updated:

A user on the Apple Developer Forums posted a workaround -

We recently discovered the root cause of this problem.

People who are affected can get around this (hope you are ready for this) ...

... changing the time zone on your assembly device away from the center of daylight. (After six weeks, you can change it and people in Mountain Standard TIme will be affected.)

No seriously. Give it a try.

Post has been edited: cde at 3:34 PM

+7
source

Sounds like corruption; maybe your Xcode installation is bad or maybe something happened when you installed Snow Leopard.

Or maybe your project is somehow running.

If you have access to another Snow Leopard machine, do a test there. If it still crashes, enter the error through http://bugreport.apple.com/

+2
source

I feel the same way too. After I could not start the old mu project (which was developed in leopard and Xcode 3.1), I tried to create a new project in Xcode 3.2 and added a new target for unit testing, added new files and a dummy case, again Xcode is hung .. No other option, I had to make him go out.

+1
source

at this link http://www.artin.org/geekblog/2009/09/xcode-snow-leopard-logical-unit-tests-hanging/

changing your time zone in PST allows this.

Interestingly, I have this problem on my macbook pro, but not on my mac pro.

+1
source

Another issue that you should pay attention to (although it may not be an OP problem) is that your unit test package is hosted on a test platform (your application), and this is a problem with the initialization of the application, your tests will freeze.

There is rdar: rdar: // 7333645 here, which suggests not initializing NSApplicationMain

The diagnosis for this is to make an assembly. If it freezes, stop the build.

Manually try to run the application (Cmd-Option-R or Cmd-Option-Y) - if the application does not appear, check the console.

+1
source

Apple posted a working file and a demo test project here: https://developer.apple.com/library/ios/#samplecode/iPhoneUnitTests/Introduction/Intro.html

Just add: Xcode324iOS41TestSuiteWorkaround.m to your test object, and everything will magically work :)

0
source

All Articles