Sonoma, with Xcode 15 and iOS 16.4 was indeed helping but Xcode won't let me delete iOS 17 images to save disk space. Because if I do, then it says get iOS 17.0 and doesn't let me use iOS 16.4 emulator runtime image until I download the iOS 17.0 runtime image again wasting my disk space. Also found that UITextView causes major memory leak(for 8MB text input pasted from clipboard, eats up 8GB RAM on SIM and OOME on device (3GB RAM limit per app)) when font is set to custom scaled font. This is not reproducible on iOS 16.4 Sim, but is reproducible on my iPhone 14 pro (17.0.3) and Sim (17.0.1) which I had to install to test this particular issue. Already wasted 2 days on this thinking it is some memory leak in my implementation or my app, but found out that UITextView From UIKit itself is implemented badly such that it eats up RAM just like that. Had to create a minimal reproducible example to isolate that root cause is indeed in UIKit. If at all Apple is listening, Please don't release untested SW, because your SW is the foundation for us devs to rely on and not go behind the rabbit hole of framework issues.

issue is still present on Version 16.0 (16A242d), simulator Version 16.0 (1038), iOS 15.0 simulator runtime

2025 and we still don't have a graph editor :(

wow just stumbled on this hard wall today, on iOS 18.6 simulator where I had a recursive navlink for folder browser. spent almost half a day on this the code was something like import SwiftUI struct Folder: Identifiable { let id = UUID() let name: String var subfolders: [Folder] = [] var files: [String] = [] } struct FolderView: View { let folder: Folder var body: some View { List { ForEach(folder.subfolders) { sub in NavigationLink(destination: FolderView(folder: sub)) { Text(sub.name) } } ForEach(folder.files, id: \.self) { file in Text(file) } } } } struct MainView: View { @State var selectedTab = 0 let folder = Folder(name: "Root") var body: some View { TabView(selection: $selectedTab) { Text("List View") // UNCOMMENT TO TRIGGER BUG: // .navigationTitle("List") .tag(0) FolderView(folder: folder) // UNCOMMENT TO TRIGGER BUG: // .navigationTitle("Files") .tag(1) } .tabViewStyle(PageTabViewStyle(indexDisplayMode: .never)) } } struct ContentView: View { var body: some View { TabView { NavigationStack { MainView() // UNCOMMENT TO TRIGGER BUG: // .navigationTitle("Main") }.tabItem { Text("Tab 1") } NavigationStack { Text("Empty View") }.tabItem { Text("Tab 2") } } } } #Preview { ContentView() } The issue doesnt happen if one uses separate navStack without nesting for each item in the nested tabView with pageStyle in my case, but that means it will feel as if we are having 2 separate screens while swiping to next page

this issue occurs only when navtitle is .large or implicitly .large, doesn't matter if one is using custom back button or hiding the back button.