This issue appears to be resolved with Xcode 26 beta 3. Thank you.

I just ran into this with Xcode 26 beta 3 as well. I just left the "fetching" window running and after a minute or two it started to download the iOS 26 beta 3 components. Be patient.

Not fixed in beta 3. I was able to build and sign using some manual provisioning but when I try to run I get the same issue shown in post #4 above with the "Could not launch ..." screenshot. I'm running a macOS 15.5 host with macOS 26 beta 3 guest running Xcode beta 3. When I try automatic provisioning, I get an error about the device not being registered. When I click on the Register Device button I get a new error about the device already exists on the team and an error about no profiles being found.

All bug reports need to be filed using Feedback Assistant.

See this thread: iOS 26 UIKIt: Where's the missing cornerConfiguration property of UIViewEffectView?

See https://developer.apple.com/forums/thread/787576?answerId=846523022#846523022 and my follow-up reply.

@mehulFunnmedia I've been using glass alternate icons since beta 1. Can you clarify what's changed in Xcode beta 3?

Never expect any response to any feedback you submit via Feedback Assistant. It will either get fixed or it won’t. I’ve filed well over a dozen beta bug reports in the last 4 weeks. 3 have been fixed with no feedback. I’m hoping the others get fixed in a future beta. And most of my reports are clearcut bugs that include a trivial app and instructions for reproducing the issue. Also keep in mind, based on the feedback numbers, Apple is getting around 20,000 bug reports per day right now! That’s way too many to expect personal feedback. As for this specific question, don’t expect Apple to reverse its decision on window resizing. Your best solution is to accept that “requires full screen” is going away. But you can set the window’s minimum size in the scene delegate so the user can’t make your window too small.

Not just you. I'm seeing this new issue as well with Xcode 26 beta 3.

Saw this on stack overflow earlier today. See https://stackoverflow.com/questions/79696251/incorrect-uitabbar-appearance-in-ios-26 There is an answer with a workaround.

I really miss that feature too. Related: https://developer.apple.com/forums/thread/791342

You can't eliminate the traffic light but you can specify its style a bit. In UIKit you can implement the UIWindowSceneDelegate method preferredWindowingControlStyle(for:) and return one of three styles. I don't know the SwiftUI equivalent.

See https://developer.apple.com/forums/thread/792269 which leads to yet another thread with more info.

#if !os(visionOS) // some code used on all platforms except visionOS #endif But is it really needed? You can let the code compile for visionOS, just don't release your app for visionOS. In App Store Connect, for your iOS app, under Pricing and Availability, you can uncheck support for visionOS (Apple Vision Pro).

Are you referring to UIAlertController? You don't need an anchor. Just create the alert and present it. It will appear in the middle of the screen. Nevermind. I just noticed this is posted in the SwiftUI section. My answer is for UIKit.