When i use the MFMailComposeViewController in visionOS, there is no cancel button for the controller. The button at the bottom closes the app. Is anyone else experiencing this? if([MFMailComposeViewController canSendMail]) { MFMailComposeViewController* controller = [[MFMailComposeViewController alloc] init]; controller.mailComposeDelegate = (id <MFMailComposeViewControllerDelegate>)view; [controller setToRecipients:toAddresses]; [controller setSubject:subject]; [controller setMessageBody:body isHTML:isHtml]; [view presentViewController:controller animated:YES completion:nil]; }

Anybody else having a problem using the segment control in visionOS. My setup has 3 segments. But after I tap segment 2 or 3 then the next tap returns focus to segement 1 not matter what segment I actually tap and then no further taps on segment 1, 2 or 3 trigger the valuechanged event and it appears that segments 2 and 3 are disabled. To diagnose this I added a to the view but I did not wire it up to anything and got the same results so it not my code causing this behavior. Any ideas?

Does anyone know if a macOS AppKit app that supports back to macOS 10.10 be added to and existing iOS that supports back to iOS 9 so they combine to be a universal purchase? Also does anyone know what the oldest version of iOS and macOS support universal purchase? FYI, the Mac app is NOT Catalyst based, just plain AppKit.

So I'm trying upload a macOS just plain old AppKit (not catalyst) binary to app store connect I get the following error: ERROR ITMS-90283: "Invalid Provisioning Profile. The provisioning profile included in the bundle .... [.....pkg/Payload/AppName.app] is invalid. [Invalid 'com.apple.application-identifier' entitlement value.] For more information, visit the macOS Developer Portal." I have tried automatically signing binary, i have tried manually signing the binary with a newly created provisioning profile, but I get the same error. Interestingly enough the provisioning profile becomes invalid on developer portal a few minutes after I try manual signing. Any ideas what could be causing this. I'm using the same bundle id from the existing iOS I thought that was the key. Any suggestions