Background: I have been stuck on this annoying problem for days, trying different solution and searching apple developer forum, stackoverflow etc for answers; some have had similar problems but no suggested solution had the desired effect.
The problem is that when updating an observableObject or environmentObject down the navigation hierarchy view stack, the views get popped back to root. Viewing data from observableObject is fine, but not editing.
Scenario is:
- I navigate to: root -> view1 -> view2.
- I update the environmentObject in View2 but then I get pushed back to: root -> view1
I have simplified my app in order to make it more understandable. See below:
ObservableObject:
class DataStore: ObservableObject {
static let shared = dataStore()
@Published var name : Int = ""
}
RootView:
struct ContentView: View {
@StateObject var dataStore = DataStore.shared
@State private var isShowingView1 = false
var body: some View {
NavigationView{
VStack{
Text(dataStore.name)
NavigationLink(destination: View1(), isActive: $isShowingView1) { }
Button(action: {
isShowingView1 = true
})
}
}
}
}
View1:
struct View1: View {
@EnvironmentObject var dataStore: dataStore
@State private var isShowingView2 = false
var body: some View {
ScrollView{
VStack(alignment: .center) {
Text(dataStore.name)
NavigationLink(destination: View2(), isActive: $isShowingView2) { }
Button(action: {
isShowingView2 = true
}){
Text("Go to View2")
}
}
}
}
}
View2:
struct View2: View {
@EnvironmentObject var dataStore: dataStore
var body: some View {
ScrollView{
VStack(alignment: .center) {
Text(dataStore.name)
Button(action: {
dataStore.name = "updated value"
}){
Text("Update data")
}
// When updating this environmentObject the viewstack will be pushed back to View1. If view2 had been navigated to view3 and the view3 had been updating the environmentObject, then it would also be pushed back to View1.
}
}
}
}
Solution: I spent many hours searching for solutions and trying different approaches, but nothing I tried worked. There seemed to be a few other people that had the same problem as I experienced, but the suggested solutions didn't cut it. But then I stumbled on a solution for this problem when trying to implement another feature. So to be frank I am writing here now, not to ask this great community for help, but instead to give back to the community by providing the this solution to others that might need to see this.
The solution is really simple implement but was not so easy to come across. If you experience a problem similar to me then you will only need to update your rootView accordingly:
RootView Updated:
struct ContentView: View {
@StateObject var dataStore = DataStore.shared
@State private var isShowingView1 = false
var body: some View {
NavigationView{
VStack{
Text(dataStore.name)
NavigationLink(destination: View1(), isActive: $isShowingView1) { }
Button(action: {
isShowingView1 = true
})
}
}
.navigationViewStyle(.stack)
//ADD THIS LINE ABOVE
}
}
This one line .navigationViewStyle(.stack) fixed the problem of popping the viewstack for me. Unfortunately I can't provide you with the logic explanation for this behaviour, but it works and I am satisfied with that. Perhaps you are too, or perhaps you have insight on why this solution actually achieves the desired effect of allowing views down the hierarchy update observableObjects without being popped.
Happy coding :)
The solution is really simple implement but was not so easy to come across. If you experience a problem similar to me then you will only need to update your rootView accordingly:
RootView Updated:
struct ContentView: View {
@StateObject var dataStore = DataStore.shared
@State private var isShowingView1 = false
var body: some View {
NavigationView{
VStack{
Text(dataStore.name)
NavigationLink(destination: View1(), isActive: $isShowingView1) { }
Button(action: {
isShowingView1 = true
})
}
}
.navigationViewStyle(.stack)
//ADD THIS LINE ABOVE
}
}
This one line .navigationViewStyle(.stack) fixed the problem of popping the viewstack for me. Unfortunately I can't provide you with the logic explanation for this behaviour, but it works and I am satisfied with that.
