Swift 6

A unit test in Swift Testing.

Appears to have been fixed in beta 6 @Frameworks Engineer :-)

We have a transparent proxy extension and a container app and both are written in swift. We use MDM for configuring the transparent proxy extension. Customer machine can have different product with another transparent proxy extension. This can be deployed via MDM or manual installation. Our requirement here is if a machine has more than one transparent proxy installed from multiple container apps(through multiple products), then is there any way we can control the order of receiving the network traffic to these transparent proxy extensions? If yes, how can we achieve this?

What do you mean by “test case” in this context? A unit test running using XCTest? Or Swift Testing? Or something else? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Well, that’s interesting. I’ve seen a raft of weird problems with C++ interop, but this specific one doesn’t ring any bells. And it’s still weird that you only see it on one machine. I tried reproducing this with a simple test project here in my office — using both XCTest and Swift Testing — and couldn’t. But that’s not a big surprise because of the above-mentioned mystery. The next step is to start gutting your main app. That’ll either reveal more interesting info about what’s triggering the problem, or it’ll get you to a small test project that you can share with us for further analysis. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='853507022, DTS Engineer, /thread/796679?answerId=853507022#853507022'] I thought we’d sorted that out already [/quote] I was right, but the info is tucked away: The PIR side of this is documented in the PIRService open source Swift package. The How to onboard with an Oblivious HTTP relay hosted by Apple section has links to the submissions forms. Scroll down to the bottom. Oh, and don’t forget to post a bug about regarding your inability to filer locally on the Mac. I’d like to get that sorted out. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I don't understand. Aren't all these tools you mention (Zombies instrument, ASan, Main Thread Checker etc.) meant to be run in Xcode or Instruments? Or are you saying I should enable some compiler flag in my production build? They're intended to run in your development build. Let me jump back to what you're saying here: since the crash reports are downloaded by Xcode from other users and I cannot reproduce it myself... What you're saying here is testing in Xcode won't help because I can't reproduce the issue. The problem with that statement is that it misunderstands how the tools above actually work. They don't just provide better diagnostic data about a crash that would otherwise occur, they actually CREATE crashes that would otherwise NOT occur. Jumping back to my description here: However, what the Zombies instrument actually does is modify the dealloc method so that freeing an object doesn't ACTUALLY free that object, but instead replaces it with an intentionally invalid object (the zombie). That means th

Presumably Xcode 26 beta 6 will be released next Tuesday and that should support iOS 26 beta 6. It’s unusual that Apple released iOS 26 beta 6 only a week after beta 5 and likely a week before Xcode 26 beta 6 comes out. In short, no there is no iOS 26 beta 6 simulator yet.

@DTS Engineer I was hoping the evolution of the relationship of QUIC and the new API you mentioned would happen during the 26 beta period. But at this point it seems that it will be impossible to receive QUIC connections using the new APIs in iOS/iPadOS 26 and I'll likely have to wait another year or hope for changes in a dot release? As far as I can tell there have been no changes to the API in this respect as of beta 6, correct?

Still happens in beta 6