Long story short, Swift is mostly about politics.

Hi Quinn and Uoptaget We have exactly the same issue and the official answer provider by Apple (Feedback ID FB11963304) is to prevent the use of DoH by replying to _dns.resolver.arpa queries with NXDOMAIN in the DNS proxy provider. As Uoptaget said above this is clearly an overlook by Apple that makes the DNS Proxy Extension practically useless and the workaround actually disable an important security feature. Where is that attention to security that Apple is so proud of? It seem it doesn't count every time... :-( Also this is a not so new issue, still present in Ventura 13.2 after four months that have been reported, on a beta version... Despite your very valuable help, to develop a DNS proxy network extension is being a nightmare... Frankly I'm quite disappointed of the lack of complete documentation and the other issues that are present (even after years) in the NE framework, some really blocking but pretty easy to spot with real QA. Well it looks like the maxim "the customer is the QA" is valid also for Apple... If it may help to have it fixed for good, should I file the same bug again or is there a wait to add +1 to it? Best regards, Luca Severini

Hello, Same issue here. We are in the same situation (an iOS app connecting to bluetooth devices using Core Bluetooth framework) and when we submitted the app for TestFlight Beta we got exactly the same response, up to the commas. Is there anybody here with experience on this matter who could kindly give some quick and effective advice? What is the string for the bluetooth protocol that we must add to the key UISupportedExternalAccessoryProtocols in plist file? Thank you! Luca Severini

Today is August 22 2024. Same problem (aside that those web pages are terrible).