DatabaseStack | database technology stack , including MS SQL Server | SQL Database library

Try either one of these.

One: I experienced something similar in my project.

I found that there were problems with the auto generated headers of Core Data entities. Try deleting from:

/Users/**user**/Library/Developer/Xcode/DerivedData/**AppName**/Build/Intermediates/**AppName**/Debug-iphonesimulator/**AppName**.build/DerivedSources/CoreDataGenerated

then clean your project with command+shift+K

Then try building.

Two: Try using let fetchRequest = NSFetchRequest(entityName: NSStringFromClass(T.self))

Swifty style of 2nd approach, works 100%:

You can pass down the parameters from the parent stack like this:

This is still not safe. The documentation explicitly stating this in the latest article, describing concurrency and queues:

NSManagedObject instances are not intended to be passed between queues. Doing so can result in corruption of the data and termination of the application. When it is necessary to hand off a managed object reference from one queue to another, it must be done through NSManagedObjectID instances.

You retrieve the managed object ID of a managed object by calling the objectID method on the NSManagedObject instance.

https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/CoreData/Concurrency.html (at the bottom)

Using methods like perform assumes that you do implement atomic actions with the context (e.g create MOs and save them OR fetch MO and extract data for requesting logic etc.)

This is an example of direct communication between controllers.