Using @ObservedObject would lead to bugs if the view also had @State properties, because changing the state would reinstantiate the viewmodel. This came up recently on a project where we stopped getting updates after a state change because the viewmodel was being recreated without calling activate() again.
Using @ObservedObject would lead to bugs if the view also had @State properties, because changing the state would reinstantiate the viewmodel. This came up recently on a project where we stopped getting updates after a state change because the viewmodel was being recreated without calling
activate()
again.