WWDC22 SALE: Save 50% on all my Swift books and bundles! >>

SOLVED: No ObservableObject found

Forums > Swift

Getting this error in my main :

Thread 1: Fatal error: No ObservableObject of type Entries found. A View.environmentObject(_:) for Entries may be missing as an ancestor of this view.

import SwiftUI

@main
struct SimpleBreadApp: App {
    @EnvironmentObject var items : Entries

    var body: some Scene {
        WindowGroup {
            ContentView()
                .environmentObject(items) // here is the error
        }
    }
}

   

How have you defined your class for Entries. It should conform to ObservableObject.

Also where have you defined your StateObject to create an instance of the envronment object? It should be here in the App , after the open brace.

Also the @EnvironmentObject should be moved to the view that uses the environment object.

class Entries: ObservableObject {
// code here, etc.
}
@main
struct SimpleBreadApp: App {
    @StateObject var items : Entries

// init() {   }   might be needed here if the StateObject is not initialised
//
//  init() {
//      let items = Entries()
//      _items = StateObject(wrappedValue: items)
//  }

    var body: some Scene {
        WindowGroup {
            ContentView()
                .environmentObject(items)
        }
    }
}
// in some view code file
struct MyView: View {
    @EnvironmentObject var items: Entries
…

   

Hacking with Swift is sponsored by Emerge

SPONSORED Why are Swift reference types bad for app startup time, and what’s the performance cost of protocol conformances? That’s just a couple of the topics you can learn about on the Emerge blog — written by the app performance experts behind Emerge’s advanced app optimization and monitoring tools, based on their experience of working at companies like Apple, Airbnb, Snap, and Spotify.

Find out more

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.