automatic-ref-counting

The object is deallocated in ARC mode and causes crash. My code below; BlockAlertView* alert = [BlockAlertView alertWithTitle:title message:message]; [alert setCancelButtonWithTitle:NSLocalizedString(@"No", @"No Button") block:nil]; [alert addButtonWithTitle:NSLocalizedString(@"Yes", @"Yes Button") block:^{ //Do Something }]; [alert show]; It appears the correct alert view(which is custom UIView) but when I click one of the button it crashes. The crash log; 2015-04-07 22:28:17.065 Test[3213:781570] <BlockAlertView: 0x16bb4160> 2015-04-07 22:33:01.746 Test[3213:781570] *** -[BlockAlertView

I am getting an error Implicit conversion of an Objective-C pointer to 'void' is disallowed with ARC -(void)openAnimation { NSValue *contextPoint =[NSValue valueWithCGPoint:self.view.center]; [UIView beginAnimation:nil context:contextPoint]; // getting error here } Can anyone help me to solve this error Thank you So first, I would point out that this type of thing is easier to do with the block based animation methods. For iOS4 and iOS5, Apple recommends that you use those newer methods instead . But to answer your specific question, the context parameter is a void *. ARC doesn't (can't)

I just installed Xcode 5.1 and found that it definitely requires projects to use ARC. I get error: garbage collection is no longer supported when trying to compile Core Plot (version 1.4). Out of curiosity I told Xcode to convert Core Plot to ARC. But it fails with ARC forbids Objective-C objects in struct in file CPTPlatformSpecificFunctions.m . I don't want to dive into Core Plot and break something by trying to fix this or similar errors. Is there a compiler setting I have overlooked? Or will there be a Core Plot version which uses ARC soon? Thanks, Dirk Xcode 5.1 doesn't require projects

I think I have a pretty good understanding of ARC and the proper use cases for selecting an appropriate lifetime qualifiers ( __strong , __weak , __unsafe_unretained , and __autoreleasing ). However, in my testing, I've found one example that doesn't make sense to me. As I understand it, both __weak and __unsafe_unretained do not add a retain count. Therefore, if there are no other __strong pointers to the object, it is instantly deallocated (with immutable strings being an exception to this rule). The only difference in this process is that __weak pointers are set to nil, and __unsafe

I have a table view as an IBOutlet , and by default XCode sets its property to be strong rather than weak . Sometimes I get a "recieved memory warning" message. So I tried to change many properties from strong to weak , but it doesn't seem to affect the process and things work smoothly. Should I set the outlets to weak, or am I wrong? And most importantly, should I set ALL properties to nil in the viewDidUnload method, or only the IBOutlet s? Rohit Gupta You should set only Strong properties to nil in viewDidUnload . Weak Properties are automatically set to Nil if the destination object is

I'm creating an application for iOS 5 and I'm drawing some gradients. The following gradient code I've always used before ARC, but now it does not work on my device anymore (however, it works on the simulator) when I use it several times (so I suppose it's a memory management issue). Anyways, here's the code: CGColorSpaceRef colorSpace = CGColorSpaceCreateDeviceRGB(); CGFloat locations[] = { 0.0, 1.0 }; NSArray *colors = [NSArray arrayWithObjects:(__bridge id)startColor, (__bridge id)endColor, nil]; CGGradientRef gradient = CGGradientCreateWithColors(colorSpace, (__bridge CFArrayRef) colors,