A Summary of the WWDC25 Group Lab

[quote='846261022, MartinSchultz72, /thread/788895?answerId=846261022#846261022, /profile/MartinSchultz72'] Is this the expected rights setup? [/quote] Nope. Here’s what I see with an equivalent test: % cd Test788895C 27-06-2025, 14.36.xcarchive/Products/Applications/Test788895C.app/Contents/_CodeSignature % ls -l total 8 -rw-r--r-- 1 quinn staff 2200 27 Jun 14:36 CodeResources This is Xcode 16.4 on macOS 15.5, but I would expect to see rw-r--r-- permissions for all versions of Xcode and all versions of macOS. Hmmm, so it’s an environmental issue. Interesting. If you’d asked me to bet on this, I would’ve put my money on it being a project issue. But, hey, that’s why we check these things. I have a couple of new diagnostic tests for you. The first is a simplification of my original test: In step 2, give the app a unique bundle ID. In step 3, disable automatic code signing and select Sign to Run Locally in the Signing Certificates popup. I’m hoping this continues to reproduce the problem. If not, stop now and w

Follow-up to Tad's question above, we have tried to use Network.framework (indirectly via the use of SwiftNIO Transport Services), which allows us to access the TLSOptions configuration. I am using the following APIs in Security.framework. https://developer.apple.com/documentation/security/sec_protocol_options_set_tls_resumption_enabled(::) https://developer.apple.com/documentation/security/sec_protocol_options_set_tls_tickets_enabled(::) When enabling both options above, (TLS 1.2) session resumptions work, but the session ticket is only reused once (the pattern is consistent across multiple requests in our testing). Using the same setup but setting the minimum TLS version to 1.3, session resumption does not work at all (the client never sends the pre_shared_key extension in the ClientHello packet with the necessary information for resumption). Our goal is to make session resumption work for TLS 1.3. Here is the simple HTTP Client that we are experimenting with. final class NIOPlayerSession { private let boot

Hi, I have the same issue. It was there in Beta1 as well, and I spoke to someone in the WWDC labs and they acknowledged it was an issue they were working on, but doesn't look they have fixed it for Beta 2. Happens when building in Xcode Beta 2 on macOS26 Beta 2 as well. I filed FB18411347

Adding nonisolated to my struct fixed the issue. My project is, as well, on MainActor default isolation mode. Although this fixes the problem, I am not sure about any repercussions that this might have in terms of concurrency. I am also new to Swift concurrency (I found Embracing Swift Concurrency from WWDC25 to be very helpful if you haven't watched it already). However, I am not sure if this is intended functionality or not because the error gives very little information. Thanks for your solutions!

I just filed FB17948001, with the sysdiagnose attached. So, I was able to take a look at it today and there are definitely some oddities I don't understand. FYI, the list of things below constructed across a significant period of time, so it isn't order in any particular way nor is it necessarily prioritized. (a) One of your components (ProxyAgent) crashed twice, with a reboot in between. You can find the crash log data in the system log archive by looking for pids 1401 and 339. The crashes themselves are fairly similar, with a high thread ID GCD thread crashing here: 6 0x101581398 -[ExtensionLoader asyncControlProxyWithErrorHandler:] 7 0x10102cebd -[AppBypassCollector sendAppEntry:] 8 0x10157e847 -[AppEntryCollector addName:] 9 0x10102d2a2 AppBypassConfig::sendListByOS(std::__1::set 0x1010226d5 AppBypassConfig::sendAppBypassList() I'm not sure how it connect (if at all), but the timing is suspicious as it lines up with about the time the system extension activation started. (b) An app update is what trig

I didn't receive some notifications for recent replies to my posts. Were notifications disabled during the WWDC25 week? Not that I'm aware of, however, I'm also not sure they've ever been entirely reliable. I'm not sure I understand the difference between temporary and working (with in progress files). Here's what I meant by that: Temporary-> One of the system provided directories (retrieved through url(for:in:appropriateFor:create:)) which are typically invisible to the user. Working-> A user visible directory that the user either directly specifies/creates. Working-ish-> (variant of #2) A user visible directory your app creates for this, probably within the destination hierarchy. For example, creating a directory like In Progress at the top level of the hierarchy you're creating. Wouldn't the temporary one be for in progress files too? In terms of how your app uses these directories, they'd all work exactly the same way. The difference between the two (and which is the right choice) reall

I didn't receive some notifications for recent replies to my posts. Were notifications disabled during the WWDC25 week? I'm not sure I understand the difference between temporary and working (with in progress files). Wouldn't the temporary one be for in progress files too? And do you mean that I shouldn't use the temporary folder in a production app?

I believe the solution to this problem is to use the new safeAreaBar(edge:alignment:spacing:content:) view modifier, as suggested by its documentation and a comment made during the SwiftUI group lab. However, I also believe that this modifier is currently broken (as of beta 2), because its behaviour seems to be no different to using safeAreaInset. I have filed feedback for this: FB18350439.