Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EXC_BAD_ACCESS in CreateCustomSubclass #27

Open
nicklocking opened this issue Apr 4, 2017 · 4 comments
Open

EXC_BAD_ACCESS in CreateCustomSubclass #27

nicklocking opened this issue Apr 4, 2017 · 4 comments

Comments

@nicklocking
Copy link

On running my app with this pod installed, I get an EXC_BAD_ACCESS in the CreateCustomSubclass method. A screenshot of the debug state at this point is attached. The variable 'class' comes in to the method fine, but something goes wrong and I'm not sure why. class_getName produces the same EXC_BAD_ACCESS if I try and add debug logging.

screen shot 2017-04-03 at 6 21 26 pm

@jerrytdev
Copy link

I see the same error as @nicklocking, even when running the example.

@batkov
Copy link

batkov commented May 18, 2017

@GrahamDennis bump

@batkov
Copy link

batkov commented May 18, 2017

Same crash while inserting object
AppStatus* appStatus = [NSEntityDescription insertNewObjectForEntityForName:@"AppStatus" inManagedObjectContext:_coreDataManager.managedObjectContext];

@fvvliet
Copy link

fvvliet commented May 19, 2017

same same...

FWIW, I added

if (!subclass) return NSClassFromString(newName);

on line 333 in GDConcurrencyCheckingManagedObject.m

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants