Visual Studio Maui IOS

In your repro steps you haven't mentioned if your app is still running between steps 4 and 5. We are aware of an issue where this might happen, and releasing and reinitializing your CBCentralManager (or restarting your app, or restarting the device) might resolve the issue. You indicate restarting the peripheral does fix it, so perhaps in your case it is the peripheral that might be causing this issue. In any case, this would be best handled by investigating further via a bug report and include a diagnostic log. Please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Bluetooth for iOS to install a logging profile on your device. Then reproduce the issue, and follow the instructions at the above link to create a sysdiagnose. And attach that to the Feedback report as well.

Started happening on Xcode 26.0.1 or were you successful with that version of Xcode? To clarify, it works properly with an iOS app upload. It is only for MacCatalyst app. So Xcode 26.0.1 works for ios and not for MacCatalyst. Have you tried today to submit one to TestFlight? I have, twice, still been getting the same issue. I will try again later today. Do you have all the logs? I have the build logs. But it is too big to attach to this reply. I will add it to the bug report.

Thanks for the quick response! I will work on that today. We've seen this happen on two devices so far with no correlation on iOS version or device. Considering our test group is only about 10 people the implication is concerning. I'll post here with a reply when I get the test project set up and sent to QA to see if we can reproduce it.

I'm experiencing a similar issue on iOS 26. When rotating the device to landscape, view.safeAreaInsets.top incorrectly returns 20pt instead of 0pt. The value only updates correctly after backgrounding the app. This was working as expected prior to iOS 26.

So Apple is unifying their version numbering across the board to roughly correspond to the coming year number (like Windows 95 or car model years for example.) I don't recall seeing this explicitly mentioned for Fairplay anywhere, but I think Version 26 has essentially replaced Version 5, with some new extra changes sneaked in. Hard to guess if version 26 certificates will work with what up to this point had been version 5, but I hope so? https://www.cnet.com/tech/services-and-software/apple-confirms-switch-to-ios-26-naming-convention-heres-why-that-matters/

Thanks for the clarification. In general, a Mac Catalyst app should behave like a normal Mac app when it comes to local network privacy. Oh, before going further I should drop a link to TN3179 Understanding local network privacy, which covers a lot of the basics here. [quote='863399022, iDevCL, /thread/766427?answerId=863399022#863399022, /profile/iDevCL'] macOS uses some set of app data [/quote] Right. Ideally, local network privacy on macOS would be able to identify code entirely by its code signature, which is how iOS works. However, things are not that simple on macOS. For example, it’s common for macOS code to be ad hoc signed [1], which forces macOS on to a compatibility path. How is your app distributed? On the Mac App Store? Or directly, using Developer ID signing? Are you sure that all the distributed copies of your app have a unique build UUID. TN3179 explains that this is critical, and also links to TN3178 Checking for and resolving build UUID problems which explains the concept in more de

Test Environment Hardware • Mac mini (2024) • iPhone 15 Software • macOS 15.6.1 (24G95) • iOS 18.0.1 (Build 26.0.1) • Apple Configurator 2.18 (10A23) • AirTrafficHost: 4025.100.103 • MobileDevice: 1818.0.1 Affected Component /Library/Apple/System/Library/PrivateFrameworks/DeviceInterface.framework/Support/deviceinterfaced

Please also see https://developer.apple.com/forums/thread/791814 We worked around it like this private class ContextMenuContainerView: UIView { override func didMoveToWindow() { super.didMoveToWindow() if #available(iOS 26.0, *) { // Make our context menu accessoryView user interactive self.superview?.isUserInteractionEnabled = true } } }