Help with NSInvalidArgumentException error

[sumosumo84]

Hi, i have spent the last hour searching for a solution. I have already tried a few different things but nothing works. The breakpoints pass evaluation. so i really don't know whats going on

info:
-no compiling errors, only this one runtime error, i have solved one of the runtime errors before but not this one.
-it gets to the first view but when it goes to lvl1 view it quits.
-here is the error :

*** Terminating app due to uncaught exception
 'NSInvalidArgumentException', 
reason: '-[EngineUI onTimer]: unrecognized selector sent to instance 0x5951700'
*** Call stack at first throw:

-here is onTimer method:

- (void) onTimer {
	
	EngineUI *engine = [[EngineUI alloc]init];

	
	[engine checkcollision];
	finalScoreLabel.text = [NSString stringWithFormat:@"%i",[engine rFinalScore]];
	
	if ([engine rBgameOver]) {
		[lvl1 removeFromSuperview];
		[self.view addSubview:gameOver];
	}
	
	
	[engine eTwo];
	
	[engine wallCollision];
	[engine ceilingCollision];
	[engine autorelease];
}

-if you need more info just ask thanks

-ps. i know i am making a new UIEngine each time onTimer is called

-Nib info:

-UIEngine is a UIViewController, but i am using it with views from DoodleDodgeViewController not from its xib, i actually didnt creat a xib for it.

- In interface builder i am using the View Controller (the orange circle with a circle in it to hook stuff up to lvl 1.

thats all the info that i think might be apporpriate for this question, but i could be wrong. if you need more info to solve it please, just ask

[sumosumo84]

if you need the UIEngine class to figure this out just post. and i will give

[sumosumo84]

please can anyone help?

[smasher]

-[EngineUI onTimer]: unrecognized selector sent to instance 0x5951700'

This means that someone is trying to call the onTimer method on an instance of the EngineUI object, but EngineUI does not have an 'onTimer' method.

The obvious error would be calling onTimer on EngineUI; that should be easy to check for. A nonobvious reason would be calling onTimer on an object that was over-released - the message would be sent to the new object which replaced the old, over-released one.

So, check all the lines in your program that call onTimer. Are you calling it on the right object? Did you over-release that object?