Visual Studio Maui IOS

I'm self-hosting a web project called mempool (https://github.com/Retropex/mempool). This project is entirely self-hosted on my own infrastructure, so I have advanced control to be sure it's just not an anti-DDoS feature that makes the bug happen. If you haven't already, please do the following: You can do the testing below on any machine you can reproduce the issue on. I'd probably use a Mac, but you can use iOS if that's simpler. However, with whatever machine you’re testing with, try and use the most minimal system possible. Ideally, that's a device that's just been reset, but using a newly created account works reasonably well on macOS as long as there isn't too much 3rd party software running system-wide. The key here is that having less on the machine minimizes the risk of private data leaking and extraneous log noise. I'd recommend installing the mDNSResponder and Network Diagnostics on the device. Those might not be necessary, but both of those increase the level of network diagnostic data, a

@pcfist Thanks for the confirmation. I'll give it a try when I get a chance. Unfortunately I am spending most of my time finding and reporting macOS/iPadOS/iOS 26 bugs that are impacting my app. Then I waste time trying to find work arounds since Apple isn't fixing any of the issues.

Thank you for your post. While I appreciate the description, I do not observe any issues assigned to the UICollectionView for iOS 26. However, I would recommend providing a focused sample project that demonstrates the issue. If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. Albert Pascual
  Worldwide Developer Relations.

While updating our test devices to iOS 26, we noticed that the connection between devices is flaky. Often when connecting to a peer from a device running iOS 26, we can observe the invite coming through and when accepting said invite, both ends go to .connecting state and a while later go back to .notConnected within the peer(_ peerID: MCPeerID, didChange state: MCSessionState) function. This happens regularly, and retrying the invitation process several times usually resolves it. Have you filed a bug on this, and if so, what is the bug number? Does anyone have any information or guidance on how to resolve this issue? Well, unfortunately, my (and Quinn's) longstanding advice has been to move to a new API and stop using MultipeerConnectivity. Quinn actually has an extended forum post describing how to move to the Network framework. I'd also suggest taking a look at the Building a custom peer-to-peer protocol sample, which uses the Network framework to implement something very similar to what

We appreciate your interest in participating in the forums! These forums are for questions about developing software and accessories for Apple platforms. Your question seems related to a consumer feature and is better suited for the Apple Support Communities https://discussions.apple.com/welcome I would recommend to provide the support team more information about what version of iOS did you update to. Albert Pascual
  Worldwide Developer Relations.

So we have an iOS app with a companion watchOS app in the project, both sharing some basic UI components we’ve created. It is possible to use UIDesignRequiresCompatibility on iOS to opt-out temporarily from transition to Liquid Glass (our design and components need to adapt). The unavailability to opt-out on watchOS may result in design inconsistency in our application between platforms. Thank you for confirmation though. We’ll have to find another solution.