What's a reliable way to make an iOS app crash?

Question

I want to test my app\'s crash reporting out in the field by deliberately having it crash when the user performs a particular action that a real user is unlikely to do accid

Answer 1

abort(); causes abnormal termination… That is a crash.

Answer 2

I use

[self doesNotRecognizeSelector:_cmd]; 

Answer 3

in Objective-C use C directly to cause a bad access

strcpy(0, "bla");

Note: while this works on any system I know -- in a future version of the C runtime OR the compiler this might not lead to a crash anymore. see Is null pointer dereference undefined behavior in Objective-C?)

(in swift you would have to bridge to objC to do this)

Answer 4

I would just kill the process normally:

kill(getpid(), SIGKILL);

So if you install a handler with signal you can also handle the crash, finishing to write opened files and these things.

Answer 5

Try this:

- (IBAction)Button:(id)sender
{
    NSArray *array = [NSArray new];
    NSLog(@"%@",[array objectAtIndex:8]);
}

Answer 6

Most popular one - unrecognised selector crash:

NSObject *object = [[NSObject alloc] init];
[object performSelector:@selector(asfd)];

Make sure you don't have -asdf method implemented in that class haha

Or index beyond bound exception:

NSArray * array = [NSArray array];
[array objectAtIndex:5];

And of course kill( getpid(), SIGABRT );