This still happens with Xcode 26.2 that just came out today. I have reported feedback, and also linked to this discussion in my feedback report.

I've reported this as FB18868109. I also reported the warning that appears on this (and every?) sample app about the icon (Failed to generate flattened icon stack for icon named 'AppIcon').

For the first error, you need to add an 'id' clause, like this: ForEach(menuItems, id: \.self) { menuLine in Here is an explanation of the reason for this (better than I could give): https://www.hackingwithswift.com/books/ios-swiftui/why-does-self-work-for-foreach For the second error, the ForEach statement needs to return a view, which print does not do. So you could include a Text within the ForEach, for example: Text(menuLine)

As of Weds morning (6/7/23) I haven't seen any WWDC23 sample code posted yet. I'm thinking they will do a big sample code drop by the end of the week. Hopefully soon!

My "Distribution Managed" certificate is due to expire next week. I selected "Manually Rotate Certificate" and it seemed to create a new one that expires next year. So perhaps I am good to go now? This process seems shrouded in mystery.

I get this problem too. I tried using Group{} inside both of the VStacks in my SwiftUI module. But then that resulted in this error message: The compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions on this line: var body: some View { I'm creating a Feedback Assistant request for this.

Yes the Developer app on the Mac has this problem also. Switch to the website to watch the WWDC videos. https://developer.apple.com/wwdc22/sessions/

This is answered here, to some extent: https://stackoverflow.com/questions/44410572/failed-to-register-for-boringssl-log-debug-updates

Happened for me too, thanks for the pointer to the custom symbols directory. I filed a Feedback Assistant request. I am wondering what about my custom symbol template caused this crash? Did I do something wrong or is it just a bug?