In beta 5, the first modifier seems to have been removed. Only the second solution will work. Note: you may have to use ignoresSafeArea(_:edges:) on the background colour/view for it to fill the entire screen.
In beta 5, the first modifier seems to have been removed. Only the second solution will work. Note: you may have to use ignoresSafeArea(_:edges:) on the background colour/view for it to fill the entire screen.
A SwiftUI approach can only be done from iOS 16.
You could look into using a UITabBarController and wrapping each tab’s View in a UIHostingController but that might be a bit more work on your behalf.
Doing a simple search online will yield plenty of tutorials. Each will build different apps but should have the same concept. Learning from multiple tutorials will help you gain a thorough understanding into the subject area and along the way you may pick up useful optimisation tips.
If that's not it, then another thing I could think of was when passing fruits.shuffled() to the list initialiser. Maybe this is causing the list to reload its data again and pop back to the list view.
In beta 5, the first modifier seems to have been removed. Only the second solution will work. Note: you may have to use ignoresSafeArea(_:edges:) on the background colour/view for it to fill the entire screen.
In beta 5, the first modifier seems to have been removed. Only the second solution will work. Note: you may have to use ignoresSafeArea(_:edges:) on the background colour/view for it to fill the entire screen.
A SwiftUI approach can only be done from iOS 16.
You could look into using a UITabBarController and wrapping each tab’s View in a UIHostingController but that might be a bit more work on your behalf.
Doing a simple search online will yield plenty of tutorials. Each will build different apps but should have the same concept. Learning from multiple tutorials will help you gain a thorough understanding into the subject area and along the way you may pick up useful optimisation tips.
If that's not it, then another thing I could think of was when passing fruits.shuffled() to the list initialiser. Maybe this is causing the list to reload its data again and pop back to the list view.