Check Variable Lifetimes and Optionals selectedHashtag Optional: You mentioned that selectedHashtag is an optional and it's nil when the view appears. Make sure that wherever this variable is initialized or set, it's done correctly and in a way that's consistent with how the HashtagSearchView expects it. If the HashtagSearchView is relying on this variable not being nil and you're passing nil without proper handling in the view's initialization code, it could lead to crashes. For example, if the view is trying to access properties or call methods on the selectedHashtag object that's nil, it will cause issues. You might want to add some conditional checks in the HashtagSearchView's init method (or wherever it uses the selectedHashtag) to handle the nil case gracefully, like this: openHashtag Binding: The isPresented: $openHashtag binding is used to control the presentation of the navigationDestination. Check if the openHashtag property (assuming it's a @State or @Binding variable) is being updated and managed correctly. If it's being set or toggled in an unexpected way, it could cause issues with the presentation and lead to the crash. For example, make sure it's only set to true when you actually want to present the HashtagSearchView and that it's set back to false when appropriate. You can add some print statements to debug when and how openHashtag is changing, like this:

Button("Toggle Hashtag Search") {
    print("Toggling openHashtag, current value: \(openHashtag)")
    openHashtag.toggle()
}