Mulle kybernetiK

The bug is solved in iOS SDK 6 beta 2

Please could you let me know the Radar ID? I'd like to file a duplicate as I'm suffering the same problem.

A workaround that can help in certain circumstances has been added to this question on Stack Overflow. Look for Edit 2: http://stackoverflow.com/questions/9104544/how-can-i-get-ocmock-under-arc-to-stop-nilling-an-nsproxy-subclass-set-using-a-w

Let's hope that WWDC brings good news in this regard.

Set the property to strong is not always correct.
It is if the object is responsible for the lifecycle of the property, not when, for example, the object receives the property simply as an "helper" object or a delegate.
Strong means the object is responsible to release the property, others simply use it.
Weak means the object will use the property but is not responsible to release it.

taoy wrote:Does anyone have a work around for this? I'm trying to mock a view controller for an iOS app, but the weak UI elements are experiencing this problem.

Hmm, I've just set the properties to (strong) in the view controller; not sure what the ramifications of this will be.

Does anyone have a work around for this? I'm trying to mock a view controller for an iOS app, but the weak UI elements are experiencing this problem.

Bug filed. Hope more people will submit the issue. It is very...... wired.

The bug is present even on iOS 5.1 sdk.
Bug status is open.
Maybe if others submit the same bug.....

Hi, any progress? What is the filed bug status? And, where can I find the status of bugs which are filed by other developer? Seems apple didn't have something like JIRA...

I submitted the bug.
If you submit the bug too, maybe we have more possibilities.....