Fixed DirectivesView navigation title issue by raising the ScrollView{} up one level in my VStack hierarchy so that all VStack views were encompassed by the ScrollView{}. This was not needed before and not sure why this had to be done for iOS/iPadOS 26 (what changed??), but it works now.

Still an issue with iOS/iPadOS 26.0 Developer Beta 4.

Still an issue with iOS/iPadOS 26.0 Developer Beta 3.

The issue does not appear to be with the first tab, but with navigation title and navigation stack in a set of views in a TabView (iOS) or NavigationSplitView (iPadOS). I've added the following new content to the feedback issue: ⸻ SwiftUI .navigationTitle Bug Diagnosis — iOS/iPadOS 26.0 Issue Summary • The navigation title set using .navigationTitle("Directives") in DirectivesView fails to appear on iOS/iPadOS 26.0, even when following Apple’s current SwiftUI best practices. • The same code works as expected in earlier versions (e.g., iOS/iPadOS 18.5). • The issue persists for both iPhone and iPad targets. Diagnostic Steps Taken Modifier Placement and View Structure • Tested both attaching .navigationTitle and a .toolbar (with a visible button) directly to the immediate child of NavigationStack (ZStack), and to the NavigationStack itself. • No change: Navigation bar, title, and toolbar item remain absent in iOS/iPadOS 26.0. Content Minimization Test • Replaced the entire content of DirectivesView with just Text("Test") inside a NavigationStack, using .navigationTitle and .toolbar. • Result: Navigation bar and title are still missing, confirming that the issue is not related to content, layout, or subviews. Subview Analysis • Confirmed that all custom subviews (DirectivesLogoView, DirectivesHeaderView, DirectivesSignatureView) are simple SwiftUI views with no use of navigation containers/modifiers or safe area overlays. • No evidence of .navigationBarHidden(true) or nested navigation stacks. Background Image Diagnostic • Temporarily removed and then reintroduced the background image (Image("Starfield")) to ensure it was not affecting the navigation bar rendering. • No effect on the presence of the navigation title or bar. Toolbar Item Diagnostic • Added and then removed a visible .toolbar item to test if a toolbar presence would force the navigation bar/title to appear (as sometimes required in new SwiftUI). • Toolbar item did not affect the navigation bar or title presence in iOS/iPadOS 26.0. TabView Position Control Test • Swapped the position of DirectivesView in the parent TabView to check for index-related issues. • The navigation bar/title remains missing regardless of tab order, confirming the problem is specific to the view or navigation stack context. Key Conclusion • The navigation title and navigation bar are not rendered under any tested conditions in iOS/iPadOS 26.0 for this view hierarchy, even in the most minimal NavigationStack configuration. • This is a regression or unannounced behavioral change in SwiftUI on iOS/iPadOS 26.0, not caused by content, overlays, modifier placement, or subview implementation. Action Requested • Please clarify if there are new requirements for navigation bar/title visibility in root NavigationStack views in iOS/iPadOS 26.0, or confirm this is a regression. • Requesting a fix or documentation update, since the app’s existing navigation structure now fails to show basic navigation elements in the latest OS. ⸻ In addition: Summary of the Issue: • A minimal SwiftUI view (MinimalNavigationTitleBugView) was created to demonstrate the navigation title bug. • In the Xcode Canvas preview, the navigation title for this minimal view appears as expected. • In contrast, my production app’s view (DirectivesView) does not display the navigation title—neither in the Xcode Canvas preview nor when running the app in the simulator or on device (iOS/iPadOS 26.0). Additional Diagnostic Details: • The issue does not appear to be caused by my code: • Both minimal and production views use the standard SwiftUI navigation patterns (NavigationStack, .navigationTitle attached to the direct child). • All custom subviews are simple, do not use navigation modifiers, and do not overlay the navigation bar area. • No .navigationBarHidden(true), nested navigation stacks, or unusual global environment modifiers are used. • The bug persists even when all content is reduced to a single Text view. Conclusion: • The fact that the minimal view works in preview but the production view does not—even in preview—suggests this bug is likely triggered by app structure, view hierarchy, or a change/regression in SwiftUI’s navigation logic for complex root or tab-based views. Action Requested: • Please clarify whether there are any new requirements for root navigation bar/title visibility in iOS/iPadOS 26.0, or confirm this as a regression. Thank you for your attention! ⸻ I have attempted to reproduce this bug in a minimal project that uses a TabView and NavigationStack, but the issue does not appear in the Xcode Canvas preview or in that context. The navigation title bug only occurs in my full production app. This suggests that the issue is likely triggered by real-world app hierarchy, parent containers, or app-level configuration that does not exist in minimal or preview scenarios.

Reference Feedback bug item FB17987650. I completed an extensive diagnostic and troubleshooting chat session with Xcode 26 Beta 2 Swift Assist AI Coding Assistant (ChatGPT) regarding this bug. Additional details that came out of this chat session that should be considered for this feedback FB17987650.

Also, this issue with the navigation title not appearing doesn’t happen at all on current App Store release production app running on iOS 18.5 and iPadOS 18.5 so this is a recent occurrence with the new iOS and iPadOS 26.

Update as of 6/26/25: Still same issue (No Navigation Title displayed on first tab in TabView and NavigationSplitView) when tried on iOS 26.0 Developer Beta 2 and iPadOS 26.0 Developer Beta 2, in Simulator and on device running 26.0 Developer Beta 2. More Info: iPhone 16 Pro Max Simulator 26.0, in Portrait, Navigation Title for first Tab view is blank. Turning iPhone 16 Pro Max Simulator 26.0, in Landscape, in-line navigation title appears as expected. iPhone 16e Simulator 26.0, in Portrait, Navigation Title for first Tab view is blank. Turning iPhone 16e Simulator 26.0, in Landscape, in-line navigation title appears as expected. iPad Pro 11-in Simulator 26.0, in Portrait, Navigation Title for first Tab view is blank. Turning iPad Pro 11-in Simulator 26.0, in Landscape, Navigation Title for first Tab view is blank.

As part of the 6/12/25 SwiftUI Group lab, Curt and Taylor spoke to this specifically related to use of color in liquid glass SwiftUI views and that use of color should be limited. However, they didn’t speak to how to put color back into List View outline disclosure carets that aren’t there in new iOS/iPad OS 26. I would still like to know if I can add color back into the carets. Here was my group lab question that was discussed: “I’ve noticed with the new design language, SwiftUI views appear to not use color as much. Example, color modifiers for List View items like carets. Is this intended and can developers introduce color back into SwiftUI view elements, if desired, like in iOS/iPadOS 18?”

Reference FB13820942

So, to clarify, I don't add the new Icon Composer file into the Assets, correct? I still have my visionOS App Icon asset in Assets. From your other thread you linked to, it appears my existing iOS and visionOS App Icons stay in Assets and the new Icon Composer icon gets added as a file at the top level in Project Navigator. I see you had other instructions on how to ensure both app icons are used in the respective project builds.

I am still experiencing this issue. I've updated the Feedback item FB13820942 today. If there is not a way to use color on visionOS to distinguish between parent rows that have children rows, what other visionOS capability can be used to distinguish rows that have hidden children rows from rows that don't have hidden children rows?

I wound up having to do your second piece of advice. I had to go into the project, then the project settings under general, scroll down to the area where frameworks and libraries are listed, and I saw my package listed there. I wound up having to click the minus sign to remove my package from that area. Then, I went to my Target and went to Package dependencies menu and I deleted the package reference in that location as well. Once I did another build action, I got a build error wherever I called import package in my swiftUI files. Once I clicked on the error, it asked for me to associate a package. I went and found my package locally on disk and added it. Once I did that, I went to my target build dependencies menu and saw that the package was then re-inserted and then went back to my project settings under general and found that that package had also been added to the frameworks and library section. At that point I was able to build again and with no errors. So I guess the issue is that with both Xcode 15 and Xcode 16, at least with a Reality Composer Pro package, Xcode doesn’t properly preserve a Reality Composer Pro package going into a new branch created from my main branch. This happened multiple times during my app development process this summer. I submitted this issue in a couple of radar feedbacks earlier in the summer, but they were closed supposedly because there wasn’t enough information. I’d appreciate if Apple could go look at those two feedbacks and reopen them and fix it so that whenever a Reality Composer Pro package manifest is part of a branch repository and a new branch repository is created from an existing one, that these package dependency errors don’t occur. Here are the feedback numbers: FB14829607 and FB14786606

This is consistent in Xcode 16 Beta 6 and occurs on alll my source control feature branches, as well as my main branch. Does not occur on any of my source control feature branches, nor on my main branch, in Xcode 15.4. it seems Xcode 16 is not properly handling my project‘s Reality Composer Pro package and is unable to locate the package even though it’s definitely in the path location to which the error is referring Doing a clean build folder fails. Also resetting package cache executes but does not work to fix the build error. Deleting the DerivedData folder under /Library/Developer/Xcode does not work.

Link to similar issue I recently had: https://developer.apple.com/forums/thread/761776

Apple. Please respond to this. I need Apple DTS support to understand how to fix these package build errors.