stub return value with NSNumber causes SIGKILL about kiwi HOT 15 CLOSED

You'r not missing something from what I can see; this seems like a bug. I'll look into it.

from kiwi.

Will look into this.

In the future, I'd like to request a tiny project or complete source file for specs that show bugs in Kiwi. This really makes tracking down issues quicker otherwise we may not even be motivated to take a look. It is quite a lot of effort to set up the environment to reproduce issues and the amount of time we can spend on maintenance is limited.

from kiwi.

Actually a sample project for this would be useful, I can't reproduce the problem.

from kiwi.

I ran into a similar issue last night. @lukeredpath have you gotten anywhere with it? I could try to create a sample project, but I'm currently working in against pre-release APIs and can't repro it consistently enough to do it in another project.

from kiwi.

I've hit this exact same issue:

it(@"should stub and mock stuff", ^{

    id testItem = [Item mock];
    [testItem stub:@selector(itemID) andReturn:[NSNumber numberWithInt:3]];

    NSNumber *theId = [testItem itemID];
    NSNumber *returnedId = [NSNumber numberWithInt:3];

    [[theId should] equal:returnedId];

});

The Item object is a vanilla NSManagedObject. I can extract those relevant bits out into a sample project if it would help...

from kiwi.

Running on sim on lion?

from kiwi.

Yes - I'm on 10.7.4, Xcode 4.3.3.

from kiwi.

Taking a guess at this without actually trying to reproduce it. Is itemID a dynamic property? If so, this may be a complicating factor.

from kiwi.

Any progress on this?

from kiwi.

Serious enough that will look at this as part of #176

from kiwi.

Main issue at the top of my head is that NSNumber isn't necessarily an object - memory wise.

from kiwi.

Any progress?

from kiwi.

I think the reason is, as @nheagy suggested, that itemID is a dynamic property and Kiwi cannot currently handle this. I don't know the underlying reason from the top of my head and whether it can be easily fixed. . To avoid this crash, instead of [Item mock] create an in-memory managed object context and insert the object there.

from kiwi.

Yeah, the property is dynamic, and NSManagedObject does it's own magic.
Let's leave this open, if I find some time I'll try to figure it out

from kiwi.

Closing this one, will open a new one for discussion of @dynamic / NSManagedObject properties.

from kiwi.