RemoveObjectAtIndex causes “message sent to deallocated instance”?

Declare the UIView *view reference with the autoreleasing qualifier, like so: (UIView *)viewWithTag:(int)tag { __autoreleasing UIView *view; __unsafe_unretained UIView *aView; for (int I = 0; I.

Declare the UIView *view reference with the __autoreleasing qualifier, like so: - (UIView *)viewWithTag:(int)tag { __autoreleasing UIView *view; __unsafe_unretained UIView *aView; for (int I = 0; I.

– Robert Oct 27 at 9:03 @Robert Sorry, see updated. – Jacob Relkin Oct 27 at 9:23 Thank you Jacob. Two things: 1) I had to use __unsafe_unretained instead of __weak, because I wish to maintain iOS 4 compatibility.

2) Turns out ARC was NOT turned on for that file. Dumb mistake. I had to go through and remove "fno-obj-arc" in the target->build phases->compile sources section.

– lewisanderson Oct 27 at 22:22 2 Do the original code crash even when you turned on ARC? Or do you still need to mark the local variables? – Mattias Wadman Oct 27 at 23:09.

Pre-ARC, I was careful to retain the object before calling removeObjectAtIndex:, and then to autorelease it. How do I tell ARC to do the same thing?

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions