NSInvalidArgumentException in iOS 6 #265

Closed
devigned opened this Issue Sep 29, 2012 · 4 comments

Projects

None yet

5 participants

@devigned

MR_SHORTHAND is defined.

The application runs properly under iOS 5, but when run in iOS 6 the application terminates when calling the findAll class method.

+[someType findAll]: unrecognized selector sent to class 0x3f81f8
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '+[someType findAll]: unrecognized selector sent to class 0x3f81f8'

Apple LLVM compiler 4.1
MagicalRecord CocoaPod version 2.0.3

@auser
auser commented Oct 1, 2012

I get the same thing, except:

Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFConstantString count]: unrecognized selector sent to instance 0x21284'

huh?

@diejmon
diejmon commented Oct 1, 2012

same here

@devigned
devigned commented Oct 1, 2012

This issue was caused for me b/c the code for initializing the core data stack was moved later in our initialization sequence (didn't see the commit come by), and thus was not setup prior to the first call to +[someType findAll].

It was my fault, but it would be nice if the error was a little friendlier than NSInvalidArgumentException.

Sorry for the noise.

@blackgold9 blackgold9 closed this Oct 1, 2012
@casademora
Member

if it's a language/initialization order thing, there isn't much I can do.
if you try to access a find* method prior to initializing MagicalRecord, MagicalRecord will still not be available to generate a nicer message for you. This is basically going to be under the "Is it plugged in" class of bugs/fixes.

On Oct 1, 2012, at 3:03 PM, David Justice notifications@github.com wrote:

This issue was caused for me b/c the code for initializing the core data stack was moved later in our initialization sequence (didn't see the commit come by), and thus was not setup prior to the first call to +[someType findAll].

It was my fault, but it would be nice if the error was a little friendlier than NSInvalidArgumentException.

Sorry for the noise.


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment