Crash

[Objective Zero]

Hey,

I am pretty much loading up a setup view. I am doing that by making "Setup" its own XIB (thats how I want it), then animating it on screen by using UIView animations. I am a little bit in a dilemma here on top of having a crash because if I am loading up this XIB as a subview in say my "TestViewController", and my done method which slides the subview off screen is in my "Setup" view controller, would I just do [self.view removeFromSuperView]; ?

That was my first question/dilemma.

Now the reason I made this thread was because it is crashing in that done method in my setup view controller.

Here is the console log on why it is crashing...

-[NSPathStore2 doneSetup]: unrecognized selector sent to instance 0x299130
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSPathStore2 doneSetup]: unrecognized selector sent to instance 0x299130'
*** First throw call stack:

Here is my done method...

- (IBAction)doneSetup {
    
    UIImage *buttonImage = [pictureButton imageForState:UIControlStateNormal];
	NSDictionary *accountInfo = [NSDictionary dictionaryWithObjectsAndKeys:
                                    Ln.text, @"LN", 
                                    buttonImage, @"theImage", nil];
    
    [accounts addObject:accountInfo];
	
	
	if (Name.text == nil) {
		
		UIAlertView *namealert = [[UIAlertView alloc]
								  initWithTitle:@"LN field empty"
								  
								  message:@"There is no name entered in the field"
								  
								  delegate:self
								  
								  cancelButtonTitle:@"Dismiss"
								  
								  otherButtonTitles:nil];
		
		
		
		[namealert show];
		[namealert release];
		
	}
	else if (buttonImage == nil) {
		
		UIAlertView *pa = [[UIAlertView alloc]
						   initWithTitle:@"No picture entered"
						   
						   message:@"There is no picture entered"
						   
						   delegate:self
						   
						   cancelButtonTitle:@"Dismiss"
						   
						   otherButtonTitles:nil];
		
		[pa show];
		[pa release];
		
	}
	
	//if ((buttonImage != nil) && (LN != nil)) {
    
	self.view.center = CGPointMake(160,240);
        [UIView setAnimationDelegate:self];
        [UIView beginAnimations:nil context:nil];
        [UIView setAnimationDidStopSelector:@selector(removeView)];
        [UIView setAnimationDuration:0.3];
        self.view.center = CGPointMake(160,660);
        [UIView commitAnimations];

	//}
}

- (void)removeView {[self.view removeFromSuperview];}

[Domele]

Instead of animating it yourself, why don't you just present it as a modal view?

[Objective Zero]

Its not full-screen.

[Domele]

That was fast. Anyways it looks like a memory problem because you are messaging a NSPathStore object. Obviously it doesn't have that method so it's crashing.

[dljeffery]

It's a zombie. Your object is either not being retained or you've inadvertently released it too early. Most likely you just never retained it though.

[Objective Zero]

Originally Posted by dljeffery

It's a zombie. Your object is either not being retained or you've inadvertently released it too early. Most likely you just never retained it though.

Yea I would say so too because if I take away a memory hogging feature in that view, the app still crashes with EXC_BAD_ACCESS. And what object would are we talking about here?

[Domele]

Whatever object has the doneSetup method.

[Objective Zero]

The object is a UIButton so you are saying the crash is because of the UIButton itself? If so, is it crashing because I am removing it from the superview?

[Domele]

No, like the class that implements doneSetup. Not the caller, the receiver.

[Objective Zero]

So it is the class "Setup" that is causing the crash? Little bit confused, shouldn't it be a specific NSObject that is causing it?

[dljeffery]

-[NSPathStore2 doneSetup]: unrecognized selector sent to instance 0x299130
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSPathStore2 doneSetup]: unrecognized selector sent to instance 0x299130'
*** First throw call stack:

The crash is because "doneSetup" is getting sent to NSPathStore2, instead of to your object that actually implements "doneSetup". The reason is because you under-retained or over-released your object and it got deallocated, but you're still holding a pointer to it somewhere. And so when you sent the "doneSetup" message to that pointer, it was sent to a different object than you thought the pointer pointed to.

[Objective Zero]

Which object are you talking about though? I understand everything else but just not sure which object your talking about.

[Domele]

The object that has the method doneSetup. If you were calling addSubview, the object that has the method is a UIView.

[dljeffery]

Your object that implements "doneSetup"; not sure what the class is called because you didn't show that part of the code.

Turn on NSZombies and re-test.

[Objective Zero]

Not sure what you mean by "has". What would have the method in my case? Is there anything wrong with the code I posted? Do you see anything wrong with it?

You probably think I'm a noob but I have been coding for 1+ year so I somewhat know what I am doing here.

[dljeffery]

Gah... you didn't post the relevant code. You only posted one method, which is the method you're trying to invoke but not reaching.

Seriously, just turn on NSZombie and re-run the app. Then you will know exactly where the call is originating.

[Objective Zero]

I already have NSZombie enabled, and that is what the debugger comes out with.

[Domele]

What is the name of the .m file where this method is implemented? That's your class.

[dljeffery]

Originally Posted by Objective Zero

I already have NSZombie enabled, and that is what the debugger comes out with.

In that case, the debugger will stop on the line that makes the crashing call to doneSetup. So, where does the debugger stop?

[Objective Zero]

Ok well the class name is Setup.m, so it has to be an object inside of it, right? NSZombie is only returning what I posted. I am not using allocations/leaks instrument because I don't think I need to.

[Domele]

The instance of Setup is getting released.

[Objective Zero]

On this line in my main.m

 retVal = UIApplicationMain(argc, argv, nil, NSStringFromClass([TestAppDelegate class]));

Also says:
Thread 1: SIGABRT

[iSDK]

You haven't set the button as a property of the UIViewController (nonatomic, retain), so it is never retained. I presume that the UIButton is declared as

[UIButton buttonWithType]

And therefore you are given a unretained, autoreleased UIButton. Make the UIButton a property with the attributes given above and you won't get this error.

The line where the error is occurring on is:

UIImage *image = [myAutoreleasedButton's imageForState:UIControlStateNormal]

[Objective Zero]

The button is created in IB and is not made programmatically.
I tried what you said anyway, and I get EXC_BAD_ACCESS in that same line in my last post with code.

[Objective Zero]

Even if I comment everything out of the method, it stills crashes with SIGABRT, I have no idea why. I have never seen anything like this before.

It has something do with the class itself, so it looks like I understand more whats going on but still no idea how to fix it. Also if I click anything in the view, it crashes. Why?

Also this is how I present the view, if that makes a difference...

Setup *sp = [[Setup alloc] initWithNibName:@"Setup" bundle:nil];
        [self.view addSubview:sp.view];
        sp.view.center = CGPointMake(160,660);
        CALayer *imageLayer2 = [sp.view layer];
        [imageLayer2 setMasksToBounds:YES];
        [imageLayer2 setCornerRadius:10.0];
        [UIView beginAnimations:nil context:nil];
        [UIView setAnimationDuration:0.3];
        sp.view.center = CGPointMake(160,240);
        [UIView commitAnimations];
        [sp release];