Objective-c – OCUnit on Snow Leopard VS Leopard

iphonemacosobjective c

I am working on a iPhone project that just added a second developer. The new developer got a new shiny macbookpro with snow leopard and Xcode 3.2. I am still on leopard and using Xcode 3.1.

He is getting errors trying to run the unit tests (OCUnit and OCMock are being used).

The shell script as the last step of the Test Target fails with a -1.

Any ideas as to what is happening, or suggestions to fix?

It blows up calling RunTestsForBundle but that is where we get stumped. Is RunTestsForBundle a script, but I can't find it anywhere on my hard drive?

Best Answer

I haven't had problems myself, so I can't verify this, but I've heard that Xcode 3.2.1 (for iPhone OS 3.1.2) fixes some unit test related issues as well.

Related Solutions

IPhone SDK 3.0 not detected by XCode 3.2

You must install the Snow Leopard version of the iPhone SDK (iphone_sdk_3.0_gm_seed__snow_leopard.dmg), not the Leopard copy (iphone_sdk_3.0_gm_seed__leopard__9m2736.dmg). My suggestion would be to run the following, and then install the Snow Leopard copy of the SDK again:

sudo /Developer/Library/uninstall-devtools --mode=all

R – Xcode 3.2 in Snow Leopard hangs running unit tests

I have also filed a bug report for this, 7210948. Still no response from Apple which is disheartening.

Updated:

A user on the Apple Developer forums posted a workaround -

We have recently discovered the root cause of this problem.

People who are affected can work around it by (I hope you're ready for this)...

...changing the Time Zone on your Build machine away from Central Daylight Time. (In six >weeks you can change it back, and people in Mountain Standard TIme will be affected.)

No, seriously. Give it a try.

Message was edited by : cde at 3:34 PM

Best Answer

Related Solutions

IPhone SDK 3.0 not detected by XCode 3.2

R – Xcode 3.2 in Snow Leopard hangs running unit tests

Related Topic