Visual Studio Maui IOS

Is there a way to destroy MIDIUMPMutableEndpoint again? In my app, the user has a setting to enable and disable MIDI 2.0. If MIDI 2.0 should not be supported (or if iOS version < 18), it creates a virtual destination and a virtual source. And if MIDI 2.0 should be enabled, it instead creates a MIDIUMPMutableEndpoint, which itself creates the virtual destination and source automatically. So here is my problem: I didn't find any way to destroy the MIDIUMPMutableEndpoint again. There is a method to disable it (setEnabled:NO), but that doesn't destroy or hide the virtual destination and source. So when the user turns MIDI 2.0 support off, I will have two virtual destinations and sources, and cannot get rid of the 2.0 ones. What is the correct way to get rid of the MIDIUMPMutableEndpoint once it is created?

I am encountering a critical issue where a custom background image on a UIToolbar fails to display when the app is built with Xcode 26 and run on iOS 26 beta. The exact same implementation works perfectly on iOS 18 and earlier versions. We first attempted to use the legacy setBackgroundImage method, which fails to render the image on iOS 26: // 1. Get Navigation Bar and set basic properties UINavigationBar* navBar = self.navigationBar; navBar.hidden = NO; navBar.translucent = NO; // 2. Setup the UIToolbar instance UIToolbar *toolBar = [[UIToolbar alloc] initWithFrame:navBar.bounds]; toolBar.autoresizingMask = UIViewAutoresizingFlexibleHeight | UIViewAutoresizingFlexibleWidth; // 3. Set the resizable image (This image does not appear on iOS 26) UIImage* imagePortrait = [UIImage imageNamed:@nav_bg]; UIEdgeInsets insets = UIEdgeInsetsMake(0.f, 6.f, 0.f, 6.f); [toolBar setBackgroundImage:[imagePortrait resizableImageWithCapInsets:insets] forToolbarPosition:UIToolbarPositionAny

Hello, In our app we provide a button that initiates a phone call using tel://. For normal numbers, tapping the button presents the standard iOS confirmation sheet with Call and Cancel. If RTT is enabled on the device, the sheet instead shows three options: Call, Cancel, and RTT Call. However, when dialing a national emergency number, this confirmation dialog does not appear at all — the call is placed immediately, without giving the user the choice between voice or RTT. Is this the expected system behavior for emergency numbers on iOS? 
And if so, how does RTT get applied in the emergency-call flow — is it managed entirely by the OS rather than exposed as a user-facing option? Thanks in advance for clarifying.

I am currently using an iPhone 16 Pro Max. Recently, Apple released iOS 26, and after updating to this version, I noticed a possible issue related to the Bluetooth functionality. When connecting my iPhone to Bluetooth headphones, the connection frequently disconnects and then reconnects after a short period of time. Unfortunately, this happens repeatedly, which makes the user experience very frustrating and unsatisfactory. At first, I assumed the issue came from my headphones, but it appears that many other users have also experienced the same problem. Therefore, I believe this issue may be related to iOS 26 itself.

Hey, Please help us to know how to get our payments of sales with iOS app we have, since beginning, our amount is pending with them and despite sevarel attempts they are providing the real issue and solutions for matter. Please suggest how to fix this issue.

I think in the next updates of IOS 26 that Apple should add a setting to enable/disable Liquid Glass because we all know that everybody doesnt like the new update.

Every time I insert a subclass (MYShapeLayer) into the model context, the app crashes with an error: DesignerPlayground crashed due to fatalError in BackingData.swift at line 908. Never access a full future backing data - PersistentIdentifier(id: SwiftData.PersistentIdentifier.ID(backing: SwiftData.PersistentIdentifier.PersistentIdentifierBacking.managedObjectID(0xb2dbc55f3f4c57f2 ))) with Optional(A6CA4F89-107F-4A66-BC49-DD7DAC689F77) struct ContentView: View { @Environment(.modelContext) private var modelContext @Query private var designs: [MYDesign] var layers: [MYLayer] { designs.first?.layers ?? [] } var body: some View { NavigationStack { List { ForEach(layers) { layer in Text(layer.description) } } .onAppear { let design = MYDesign(title: My Design) modelContext.insert(design) try? modelContext.save() } .toolbar { Menu(Add, systemImage: plus) { Button(action: addTextLayer) { Text(Add Text Layer) } Button(action: addShapeLayer) { Text(Add Shape Layer) } } } } } private func addTextLayer() { if let desig

I and many of my users observed the problem that the Shortcuts app seems to confuse and swap actions of different apps from the same developer. This happens after updating to iOS 26. This breaks many Shortcuts. Deleting one of the apps or re-adding the actions sometimes seems to help. Does anybody else observe this problem, or know how to handle this?

my dynamic island UI is triggering as empty when i send my curl, this is a pushToStart run push driven live activity and when i send my curl this is what appears, despite be being able to render the UI through a local push no problem, here is my curl. curl -v -H apns-topic: MuscleMemory.KimchiLabs.com.push-type.liveactivity -H apns-push-type: liveactivity -H apns-priority: 10 -H Content-Type: application/json -H authorization: bearer eyJhbGciOiJFUzI1NiIsImtpZCI6IjI4MjVTNjNEV0IifQ.eyJpc3MiOiJMOTZYUlBCSzQ2IiwiaWF0IjoxNzU4ODU2MDkyfQ.i83VbgROsxEzdgr512iQkVsp0FjHIoHq2L6IB2aL1fImJgX-XM6TM5frNnVyfva7haMd9fDGjO2D_wfCq8WnBg --data '{ aps: { timestamp: '$now', event: start, content-state: { plain_text: hello world, userContentPage: [hello world] }, attributes-type: KimchiKit.DynamicRepAttributes, attributes: { activityID: 12345 }, alert: { title: Workout started, body: We’ll show your reps on the Lock Screen., sound: default } } }' --http2 https://api.sandbox.push.apple.com/3/device/80d50a03472634d9381b729deec58

Environment: • macOS 26.0 (25A354) • Xcode 26.0.1 (17A400) Issue: Applying .tint(...) to a macOS Liquid Glass style Toggle does not change the background color when the toggle is in the on state. Expected behavior: The .tint(...) modifier should apply the chosen color. Actual behavior: The toggle remains system blue (accent color), regardless of the tint specified Notes: I’m hearing that .tint() behaves normally on iOS, so this may be macOS-specific.

Health medications appearing on apple watch is still broken. After entering medications in health app with health notification on. The medications does not appear in the Apple Watch.