@simonbs ok! A workaround that you could try until this gets fixed at the SwiftUI/Observation level is to move all the accesses to Observable class properties to a super view that does not update frequently, then take the values of those properties in as plain properties on your view that updates frequently.