@lukeredpath Thanks! When using a bare enum conforming to Identifiable, SwiftUI does animate sheet dismissal and reappear on case change, even when using a single .sheet modifier, so I was wondering.

enum State: String, Identifiable {
    case featureA = "A"
    case featureB = "B"
    
    var id: String {
        self.rawValue
    }
}

.sheet(item: $state) { state in
                switch state {
                case .featureA:
                    Text("Feature A")
                case .featureB:
                    Text("Feature B")
                }
            }

But using multiple .sheet modifiers is a valid workaround 👍

Yes, this will work but its very different to passing in a reference to a store - in your second example $state is a binding to a value so SwiftUI can easily tell when its value has changed, where as in the first example the item will always be a Store<Sheet.State?, Sheet.Action>. Perhaps it would be possible for the store to derive a unique ID when its State conforms to identifiable, I don't know.

We do have a PR to derive store identity from the state's identity: #3464. But more needs to be explored before that can be ready to merge.

Until then you can always conform Sheet.State to be identifiable and then use the sheet(item:id:) method that comes with SwiftUINavigation (which is included in TCA automatically):

extension Sheet.State: Identifiable {
  var id: AnyHashable { … }
}

// in the view:
.sheet(item: $store.scope(state: \.sheet, action: \.sheet), id: \.id) { store in
  …
}