Re: NSManagedObjectContext's undoManager is nil on macOS

2018-09-06 Thread Rick Mann
"although remember that both NSError** out parameters and exceptions are autoreleased and do not escape block lexical scope happily" That statement needs to be linked to clarification. > On Sep 6, 2018, at 12:56 , Jeff Nadeau wrote: > > This behavior changed in 10.12 for applications linked

Re: NSManagedObjectContext's undoManager is nil on macOS

2018-09-06 Thread Dave Fernandes
Ah - thank you! I should read those release notes more carefully. Will close the bug I just filed. > On Sep 6, 2018, at 3:56 PM, Jeff Nadeau wrote: > > This behavior changed in 10.12 for applications linked against that SDK or > later. It’s listed in the “Behavioral changes” section of the

Re: NSManagedObjectContext's undoManager is nil on macOS

2018-09-06 Thread Jeff Nadeau
This behavior changed in 10.12 for applications linked against that SDK or later. It’s listed in the “Behavioral changes” section of the Core Data release notes for that year:

NSManagedObjectContext's undoManager is nil on macOS

2018-09-05 Thread Dave Fernandes
The docs say: "In macOS, a context provides an undo manager by default; on iOS, the undo manager is nil by default.” However, I am finding on macOS 10.13.6, the undoManager is always nil when creating a MOC. Is this new behavior expected for High Sierra, or is it a bug?