“Visual Studio Maui IOS”

Last post ... I promise ... When I reinstalled Xcode 26.4 again after going through all of the above shenanigans, I chose to NOT install the 26.x line of simulators, nor the Predictive Code Completion Model. As before, Xcode downloaded and installed older simulators anyway, but left the 26.x options uninstalled with their Get buttons primed and ready. I closed down Xcode and did some other stuff. After an hour I launched Xcode to check on things, opened Settings and, lo and behold, the iOS 26.4 and watchOS 26.4 simulators were showing as installed under the Platform Support section of the Components. What is going on? It's as if Xcode is hallucinating.

The problem still exists on iOS 26.4

Wish I'd reported this weeks ago when my iPad showed this symptom on the iOS beta, but I'd assumed it was due to me using a sandbox user since Apple was so bullish in their WWDC 2023 video about the number of test cases they'd created for CkSyncEngine. I'd also created a feedback before discovering this thread (FB22344526) Easy to reproduce - the Apple sample app fails. Hoping it gets taken seriously.

I filed a similar report yesterday... Xcode 26.4 (17E192) Simulators Keep Showing As Unavailable After Successfully Intalling Them FB22346008 ... with sysdiagnose tarball and screen shots. Am also running Tahoe 26.4. I spent the better part of this evening removing the following items: /Applications/Xcode.app /Library/Developer ~/Library/Developer ~/Caches/com.apple.dt.* ~/Preferences/com.apple.dt.* /private/var/tmp/com.apple.CoreSimulator.SimDevice.* rebooting my machine, and then reinstalling Xcode 26.4 (Apple Silicon) and the command line tools. I then used xcrun simctl to flush all of my devices and runtimes. I spent a lot of time fighting Xcode because after removing old simulators, Xcode automatically downloads them all again (SMH!). Once Xcode seemed to stabilize its downloads (using xcrun simctl list to monitor everything), I then added the iOS, watchOS, and tvOS simulators for 26.4. So far, things seem to be behaving. We'll see whether or not I wake up tomorrow to joy or despair. I have a 20

Exactly same issue here since iOS26.4. Mac works as expected, on iOS not getting updates on cloud sync. Filed the feedback FB22353668

I guess our only two options till the next version are: a) revert to an iOS 26.2 simulator b) just preview everything in the actual Simulator and never click on the Canvas no matter what

Since updating the OS to 26.4, the app has been crashing more often after I launch it. Please post the full crash log, using the instructions found here. Additional information: The app was developed using Unity. After contacting Unity, they indicated that based on the crash logs, it is highly likely that a “Segmentation Fault” occurred. A Segmentation Fault just means your app attempted to access invalid memory, which doesn't actually tell you very much about why you actually crashed. The document Diagnosing memory, thread, and crash issues early has a good overview of the tools that can help file this sort of issue, followed by some specific examples of what can cause this kind of failure. I suspect the “Segmentation Fault” is caused by insufficient memory. No, not really. Memory exceptions (what a seg fault is) happen because you’re accessing memory that you either never allocated or have already freed, neither of which will happen due to direct lack of memory. Keep in mind that your app can't really run o

A good rule of thumb is to set your minimum deployment target based on what you're able to test on a device. The simulator is a great development aid, but it's not a replacement for fully testing your app on a device with all of the major iOS versions that you intend to support.

I was able to replicate this issue in a very simple way, within a new project created with the standard Xcode template, to which I added a Swift Package as a library (MyLibrary). This is the Package definition: // swift-tools-version: 6.3 // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package( name: MyLibrary, platforms: [.iOS(.v18)], products: [ // Products define the executables and libraries a package produces, making them visible to other packages. .library( name: MyLibrary, targets: [MyLibrary] ), ], targets: [ // Targets are the basic building blocks of a package, defining a module or a test suite. // Targets can depend on other targets in this package and products from dependencies. .target( name: MyLibrary, path: Sources/MyLibrary ), ], swiftLanguageModes: [.v6] ) If the target name is equal to library name (MyLibrary) the preview of SwiftUIView works as expected. If I change the target name (for example