“Visual Studio Maui IOS”

I am having the same issue on both of my machines (both running Xcode 26.4 and 26.4 simulators.) After setting the simulator back to iOS 26.2, I can work in the SwiftUI canvas.

Consider this: % swift demangle _$s9MetricKit10mxSignpost_3dso3log4name10signpostID__ySo03os_H7_type_ta_SVSo03OS_j1_F0Cs12StaticStringV0J0010OSSignpostI0VALSays7CVarArg_pGtF MetricKit.mxSignpost(_: __C.os_signpost_type_t, dso: Swift.UnsafeRawPointer, log: __C.OS_os_log, name: Swift.StaticString, signpostID: os.OSSignpostID, _: Swift.StaticString, _: [Swift.CVarArg]) -> () So, the problematic symbol is mxSignpost(…). According to the documentation, that’s available on iOS 13 and later. However, that’s clearly not the case O-: I see two possibilities here: The availability annotation is just wrong. The symbol is available on older system, but it moved, and the corresponding .tbd file doesn’t record that move. I suspect that it’s the latter [1] but, either way, it’s a bug in the MetricKit framework interface and you should file it as such. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.

We see this issue in iOS 26.3 as well, but it can reproduce almost every time if we build the app with Xcode 26.4 and run the app on an iOS 26.3 device. Also sent: FB22305926 with the crash log.

I am seeing zero CloudKit pushes delivered on iOS 26.4. Filed FB22367981

With iOS 26.4, a white space has now appeared above the side navigation toolbar. But only when using NavigationSplitView within TabView. I hope this gets fixed; otherwise, I’ll have to write a custom TabView. Things had been quiet for a while, but now it’s annoying me again.

[quote='820849021, AndriiSulimenko, /thread/820849, /profile/AndriiSulimenko'] Is it possible to distribute a DNS proxy provider for use on non-MDM / non-supervised devices? [/quote] No. The table in the DNS proxy section of TN3134 lists two options for iOS: app extension | 11.0 | supervised devices only | 16.0 | per-app on managed devices If you exclude those two options then you have… well… zero options. [quote='820849021, AndriiSulimenko, /thread/820849, /profile/AndriiSulimenko'] Is [this] strictly enforced at distribution/runtime? [/quote] Yes. It’s a privacy policy that’s strictly enforced at runtime [quote='820849021, AndriiSulimenko, /thread/820849, /profile/AndriiSulimenko'] Is a packet tunnel provider the only viable alternative for App Store distribution? [/quote] There are two parts to this question: Do packet tunnel providers work on general user devices? Are there a viable alternative to a DNS proxy. The answer to the first is “Yes.” TN3134 makes that clear. The answer to the second is

Thank you for your response, Richard. I have a follow-up question to clarify the exact trigger for the launch failure. Could you tell us which of the following scenarios actually causes the app to fail to launch? Built with Xcode 26 (iOS 26 SDK), run on an iOS 27 device — Does the app fail to launch simply because the device is running iOS 27, even though it was built with the older(=26) SDK? Built with Xcode 27 (iOS 27 SDK), run on any OS version including iOS 27 — Does the failure occur across all OS versions, including iOS 27(All OS versions(iOS15 or higher) supported by my app), as long as the app was compiled with the iOS 27 SDK without adopting the scene-based life cycle? Both of the above — Does the failure apply in either case? Understanding whether this is enforced at the OS level (runtime) or at the SDK/build level (compile time) is critical for planning our migration and release timeline. Thank you.

However, This UI glitch We have noticed not only on Toolbar but wherever we are using dropdown(Menu+Picker) throughout the app. It created different shapes while disappearing such as circle and capsule. In iOS 26.0 it shows capsule and iOS26.2.1 it shows circle like UI while disappearing. Is this existing issue in XCode/iOS26, If yes, When we can expect the fix from Apple?

Thanks for the update. Just to clarify: Starting from April we must use Xcode 26.X to upload apps to the App Store (using older Xcode versions will fail). In addition, Xcode 26.X deployment target is iOS 15+. So, no option to release apps targeted to older iOS versions? If this is the case, why this isn't blocked during the Xcode build process? or even during the App Store processing? Also, what about the apps we already published a week ago with target deployment 12.0?