Visual Studio Maui IOS

Also actual for iOS 26.1 Beta 2

Is there a workaround, unofficial method, or private API to generate a local hotspot from an app on iOS, similar to what can be done on Android? No APIs exist that will allow an app to turn the iOS device into a hotspot. Are there any best practices for improving the local Wi-Fi connection experience between an accessory and an iPhone in the absence of hotspot controls? We have a range of APIs an app can use to have the iPhone connect to a specific hotspot. In a modern app, that flow starts by pairing with your Wi-Fi accessory using AccessorySetupKit, then using either NEHotspotManager or our Wi-Fi aware support to actually join that hotspot. Note that while the AccessorySetupKit documentation is primarily focused on Bluetooth, that's largely because the Bluetooth process is significantly more complicated than the Wi-Fi flow. Is there an alternative within the MFi program? Nothing* in the MFi program applies to your particular situation. We do license WAC (Wireless Accessory Configuration) t

FYI - none of these issues have been resolved as of iOS/iPadOS 26.1 beta 2. Dear Apple, please fix all of these scope button issues. They are impacting my app. If you do not intend to fix these then you should mark the APIs as deprecated and suggest an alternate solution.

While there is a somewhat known issue with apsd not being able to sustain a persistent connection to APNs under certain network conditions/configurations, there is also the requirement that the devices receiving the notifications needs a persistent, non-proxied connection to APNs. Outside of the no proxy requirement, the root cause is not known, and if you can file a new bug report on this, more data would be helpful. In the meantime, you can try a different network connection, turn off any VPNs on your device, and if you have an option to not be behind a proxy things might work better. But please file a Bug Report on this In your bug report we would need some diagnostics logs as well. Please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Notifications for iOS to install a logging profile on your device. Then reproduce the issue (both before and after killing apsd), and follow the instructions at the above link to create a sysdiagnose. Attach it alo

We have this issue too. How can our iOS engineering team do their jobs without access to testflight if we adopt managed apple ids? The only reference on the topic is here: https://support.apple.com/guide/apple-business-essentials/service-access-with-managed-apple-accounts-axm171b3ee95/web which cites privacy concerns as a nebulous non-reason. Our teams that own mobile software need to use testflight to test release-track builds.

Thank you very much for your answer!. Well, the custom view controller was using the standard storyboard with UIKit, and I was adding my custom CropView programmatically. Now debugging in detail between iOS 17.5, iOS 18, and iOS 26, it seems that in iOS 26, it always shows that FloatingBarContainerView (maybe it's something related to liquid glass by default), so by code I added: let cropViewAsView = cropView as! UIView cropViewAsView.translatesAutoresizingMaskIntoConstraints = false NSLayoutConstraint.activate([ cropViewAsView.leadingAnchor.constraint(equalTo: view.leadingAnchor), cropViewAsView.trailingAnchor.constraint(equalTo: view.trailingAnchor), cropViewAsView.topAnchor.constraint(equalTo: view.topAnchor), cropViewAsView.bottomAnchor.constraint(equalTo: view.bottomAnchor) ]) And this fixed my issue, as you commented, related to the storyboard. I forgot to add the constraints layouts, and it seems that my custom crop view was starting with frame CGRect zero by default

This way of setting view controllers broke in iOS 26, causing the bug you reported: viewControllers = [firstVC, secondVC] instead, try this: if #available(iOS 26.0, *) { splitVC = UISplitViewController(style: .doubleColumn) splitVC.preferredSplitBehavior = .tile splitVC.setViewController(firstVC, for: .primary) splitVC.setViewController(secondVC, for: .secondary) } else { // your previous setup }