NEW: Start my new Ultimate Portfolio App course with a free Hacking with Swift+ trial! >>

Picker and CoreData

Forums > SwiftUI


I have two CoreData entities, "Product" and "StorageLocation"; there is a one-to-many relationship between them; "Location" can have multiple product, and product just one location. Idea behind is: User create a product a choose from a picker the location, then the product is saved and shall be saved the relationship too (location); but the picker gives me back a string, not a "Location" entity which is expected when saving a new product. Here my code:

@State private var storageLocation = "AAAA"
        sortDescriptors: [NSSortDescriptor(keyPath: \, ascending: true)],
        animation: .default)
    private var storageLocations: FetchedResults<StorageLocation>
Form {
                Picker(NSLocalizedString("storage", comment: "storage"), selection: $storageLocation) {
                    ForEach(storageLocations, id: \.self) { (storageLocation: StorageLocation) in

How can I get back from the picker a Location object?

Thanks Marco


I digged more into the topic and the problem is not in the picker actually, but in CoreData. What I have is an ActionSheet where I can create a new "Product" entity; in this sheet there is a picker to pick a storage location which is basically another entity. The function addProduct will save then to CoreData

private func addProduct(id: UUID, name: String, actualQty: Int, expDate: Date, location: StorageLocation) {
        withAnimation {
            let newItem = Product(context: viewContext)
   = id
   = name
            newItem.qty = Int32(actualQty)
            newItem.expDate = expDate

After having watched few CoreData videos/tutorials, I understood I have to use the function "addToProducts" provided by the CoreData classes. But when I do this, I get the following error:

Thread 1: "-[StorageLocation addProductsObject:]: unrecognized selector sent to instance 0x600000abcf40"

and the app crashes;

I looked for the error, but everything I found was an incosistency between model and classes, but this is not my case.

Any idea/hints?

Thanks Marco


Hacking with Swift is sponsored by Instabug

SPONSORED Catch bugs as soon as they happen and know exactly why a crash occurred. Instabug's SDK grabs all the logs they need to fix bugs, crashes and performance issues in minutes instead of days. Get screenshots, device details, network logs, repro steps, and tons of other critical insights needed to resolve issues and prioritize product backlogs straight from your dashboard. It only takes a minute to integrate!

Get started now

Sponsor Hacking with Swift and reach the world's largest Swift community!

Reply to this topic…

You need to create an account or log in to reply.

All interactions here are governed by our code of conduct.

Unknown user

You are not logged in

Log in or create account

Link copied to your pasteboard.