My production App Store app can be run on iOS/iPadOS 18 Beta. Here is the App Store link: Starship SE Corps This plus the provided code excerpts should be sufficient to view the issue in context until I have a chance to try a focused Xcode test project with the risk that a test project doesn’t show the issue like my actual production app does.

Thanks Michael. I appreciate your response. I did have a lab session yesterday and I talked to the engineer about this need that I have per the feedback number. They confirmed it doesn’t appear that there is an ability to do exactly what I want to do as I described in the feedback. I do understand that the accentcolor is deprecated, and the new tint Method is the new way to do things, however I could not get that to work either using foregroundStyle or any method related to tint. I’ll look at your code more and see if I’ve got other ideas based on that. With accentcolor deprecated, what if I still have an accent color in my assets? That accent color is still being used in my app and other areas and works just fine, just not in the area. Will the accentcolor asset in my app stop working in the future? How does tint now work relative to what I already have defined as an accentcolor in my assets catalog?

I’ll look into this. This might be what I need. For now, I went ahead and submitted a Feedback suggestion: FB13871808 (Restoring visionOS windows to spatial location upon returning from immersive scene)

Apparently there is a feedback assistant/bug that was mentioned in the Apple Developer Forums. I’ll link below. Currently, when you do the archive build, you have to set the base SDK to visionOS. I did this when I did my separate visionOS build, and it worked fine. Xcode now showing Vision Pro Archive destination. Answer from other Apple Developer forum post

Thanks so much @gchiste. That was the issue. Now working. It would be nice if the Developer Documentation page Bringing Your Existing Apps to VisionOS could be updated to address this situation more specifically. It vaguely mentions maybe having to adjust build configuration settings but does not address how to do what you show above, which I think would be a fairly common situation for developers converting their existing iOS, iPadOS apps to add visionOS functionality with RCP.

Upon further reading...it appears that the default for Section headers going forward will be to NOT show expansion arrows. To use expansion arrows, a new isExpanded parameter needs to be included in the Section initializer and will be needed to bind to a state property. I haven't gotten this new approach to work, but seems like the answer.

I use to have my Sections (with header) within a List View that was within a NavigationView. Since NavigationView is now deprecated, I've transitioned to using NavigationStack. No other changes to code, but now my section headers don't have a triangle to show/hide the section content...i.e. the section is now longer collapsible. Your code above doesn't show what your ForEach statements are wrapped in. Are they within a List?

I've recently started an app where the content view uses this type of hierarchical list view (with children). I'm able to successfully display the hierarchical list in the content view, and when I tap an item in the hierarchy, I'm successfully able to navigate to a detail view for that tapped item. I'm also able to edit one of the tapped item properties in the detail view using a TextEditor view. However, when I click save in the detail view, the changed property will only be saved if it was the parent list item row that I tapped in the content view. If it was a child list item in the content view, the save does not work. I think I may have a problem in my save code logic and I'm trying to investigate.

I talked with Apple about this during a lab session at WWDC21. They had me create a feedback ticket. Here is the Feedback: FB9156589

Apple has some excellent SwiftUI and UIKit tutorials on the developer website. The tutorials allow you to work through the specific app creation projects that teach you the various technologies for SwiftUI and UIKit. SwiftUI Tutorials iOS App Dev Tutorials

I'm having a similar problem but with an independent watch app using Swift UI. The live preview in Xcode shows a back button on the detail screen and it allows me to return to the parent (content view) screen. However, when I run the same app on the watch simulator and on an actual Apple Watch Series 6, the back button doesn't appear and I can't navigate back to the parent view.

Thank you very much! If I’m already logged into my GitHub account through Xcode using a password, do I have to log out and delete that account entry in Xcode and then create a new GitHub account and login with the token or can I just log out of the current GitHub account in Xcode preferences and then log back in with the new access token?

So how can I create that authentication token and then how do I set up my login in Xcode to GitHub to use that token instead of a password which GitHub is deprecating?