Re: NSManagedObject.managedObjectContext is nil???

2019-03-28 Thread Rick Mann
No, it wasn't deleted. It might've been refresh to re-fault everything. > On Mar 28, 2019, at 10:13 , Steve Christensen wrote: > > Is it possible that the entity is retained but has been deleted from the MOC? > I vaguely recall seeing this myself at one point in the dim past. > >> On Mar 27,

Re: NSManagedObject.managedObjectContext is nil???

2019-03-28 Thread Steve Christensen
Is it possible that the entity is retained but has been deleted from the MOC? I vaguely recall seeing this myself at one point in the dim past. > On Mar 27, 2019, at 1:18 PM, Rick Mann wrote: > > I can't tell. I don't believe I have any unreferenced MOCs. > >> On Mar 27, 2019, at 13:08 , Dave

Re: NSManagedObject.managedObjectContext is nil???

2019-03-27 Thread Rick Mann
I can't tell. I don't believe I have any unreferenced MOCs. > On Mar 27, 2019, at 13:08 , Dave Fernandes wrote: > > Just to clarify, the moc exists, but the reference to it is nil? Or has the > moc, itself, been deallocated? > >> On Mar 27, 2019, at 3:40 PM, Rick Mann wrote: >> >> This is

Re: NSManagedObject.managedObjectContext is nil???

2019-03-27 Thread Dave Fernandes
Just to clarify, the moc exists, but the reference to it is nil? Or has the moc, itself, been deallocated? > On Mar 27, 2019, at 3:40 PM, Rick Mann wrote: > > This is proving very hard to diagnose, as it doesn't always happen. I tried > observing -managedObjectContext, but it never gets

Re: NSManagedObject.managedObjectContext is nil???

2019-03-27 Thread Rick Mann
This is proving very hard to diagnose, as it doesn't always happen. I tried observing -managedObjectContext, but it never gets called with a nil value. Moreover, my entity's -dealloc method is sometimes called even though none of the -awake methods gets called. This is a complex app with a lot

Re: NSManagedObject.managedObjectContext is nil???

2019-03-27 Thread Mike Abdullah
Given the number of objects Core Data is designed to juggle, managing that number of weak references might well affect performance. Besides, wouldn’t you still the same result, that your object has a nil reference to the context because the context has been deallocated? Furthermore, I think

Re: NSManagedObject.managedObjectContext is nil???

2019-03-26 Thread Rick Mann
The implication there is that an object has a weak reference to the MOC? Ah, in the header I see it's `assign`. I wonder why they do that and not `weak`. Thanks, I'll look into it. > On Mar 26, 2019, at 14:50 , Richard Charles wrote: > > You have retained the managed object outside the

Re: NSManagedObject.managedObjectContext is nil???

2019-03-26 Thread Richard Charles
You have retained the managed object outside the managed object context. --Richard Charles > On Mar 26, 2019, at 1:04 PM, Rick Mann wrote: > > I'm seeing a situation where my NSManagedObject's managedObjectContext is > nil. It doesn't happen all the time though. Any idea why? Thanks! > > --

NSManagedObject.managedObjectContext is nil???

2019-03-26 Thread Rick Mann
I'm seeing a situation where my NSManagedObject's managedObjectContext is nil. It doesn't happen all the time though. Any idea why? Thanks! -- Rick Mann rm...@latencyzero.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not