EXC_BAD_ACCESS when calling class init in Objective C

Question

I've been trying to figure this out but I can't figure out what I'm doing wrong.

I wrote a class and whenever I try to initialize it, I get a EXC_BAD_ACCESS error. I can't even step into the initialization.

Anyone have any idea what I'm doing wrong?

User *myUser = [myUser init];

.h file:

#import <Foundation/Foundation.h>


@interface User : NSObject {
    long rowId;
    NSString *email;
    NSString *password;
    NSString *fileVersion;
}

@property long rowId;
@property (assign) NSString *email;
@property (assign) NSString *password;
@property (assign) NSString *fileVersion;

@end

.m file

#import "User.h"


@implementation User

@synthesize rowId, email, password, fileVersion;

-(id)init {

    self = [super init];
    return self;
}

@end

Be sure to understand what’s an assign property and why it’s not common for NSString* properties to be assign (hint: they’re usually copy). — user557219
– user557219, Commented Jan 19, 2011 at 23:06

Dave DeLong · Accepted Answer · 2011-01-19 23:00:57Z

11

You have to actually allocate the object:

User *myUser = [[User alloc] init];

Don't forget to release it when you're done using it.

answered Jan 19, 2011 at 23:00

Dave DeLong

243k58 gold badges452 silver badges498 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Adam Rosenfield Over a year ago

Or autorelease it upon allocation (in which case, it's usual to write a helper class method that does the alloc/init/autorelease).

netrage Over a year ago

Thanks, I was hoping it was something obvious.

Collectives™ on Stack Overflow

EXC_BAD_ACCESS when calling class init in Objective C

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related