A Summary of the WWDC25 Group Lab

Im seeing the same thing, started on 2025-08-13. Newly pushed build were no longer being added to an Internal Testing group (configured for automatic distribution)

My team is experiencing the same issue. Additionally, newly approved testflight builds are displaying a count for invites, but no internal groups have been automatically assigned or has anyone received invitations. This has been going on for ~3 days.

I have similar problem. I uploaded a version to testflight with an internal group which build distribution set to automatic. I tried to change text of the Test Details. I tried to add a dummy group with manual build distribution, and adding it to the version group. Still not working. I tried to add/change test information for the app. Not working Please help

I guess this is one way to do it. TLDR; Create a resolver view to wrap your content views. Use an environment closure to pullback values from it. Re-distribute these values using the containerValue API to propagate value to subviews. Use .onChange(of: subview.containerValues.foo)API on subview to be notified of changes. Let's say we want to design an API like that: // MARK: Client Stepper { StepView { Text(Becoming spartan) } content: { FooView() } StepView { Text(Dying in glory) } content: { BarView() } } where FooView, BarView could access to a complete closure through environment to notify it finishes (same way as @Environment(.dismiss)): struct FooView: View { @Environment(.isComplete) private var isComplete var body: some View { VStack { Text(This is the part where you become a spartan) HStack(alignment: .bottom) { Rectangle() .fill(Color.blue.gradient) .frame(width: 50, height: 25) Rectangle() .fill(Color.cyan.gradient) .frame(width: 50, height: 10) Rectangle() .fill(Color.pink.gradient) .frame(width: 5

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

Greetings, I would prefer the search field to be hidden until the search icon is clicked, like it is when the list is scrolled up a bit: However, at launch and also when I scroll to the top of the list, regardless of visibility setting, I get this: Please note, I have no commercial aspirations for this app, strictly personal use for a handfull of friends and I. We are learning to live with the search field when it appears as it can be scrolled out of view, but when present it is surprisingly distracting. Many of us, including myself, start typing in the search field to ADD an item, instead of clicking the plus icon. I confess that I am looking for a quick fix, as I know that custom tab bars and suchlike can eliminate this problem. However, I am not sure I am up to that task. I would most likely just learn to live with it as i am doing now. Thanks for any help you can provide. Here is the code: struct ListView: View { @Environment(.modelContext) private var modelContext @State private var selectedRow: String?

ISTR a bug where QUIC would have problems connecting to Bonjour endpoints (that is, NWEndpoint.service(name:type:domain:interface:)) values. Hence this request on the thread you referenced. However, I just tested this today and it seems to be work. This was on macOS 15.5. So, that’s clearly not the problem. Oh, wait, you’re creating a group. When I repeated my test with a group rather than a connection, I see exactly this trap )-: It’s trivial to reproduce: import Network func main() { let endpoint = NWEndpoint.service(name: Guy Smiley, type: _test._udp, domain: local., interface: nil) let descriptor = NWMultiplexGroup(to: endpoint) let group = NWConnectionGroup(with: descriptor, using: .quic(alpn: [test])) print(group) } main() Please file a bug about this. Once you’re done, post your bug number here and I’ll update it with my findings. In the meantime, the workaround is to resolve the service, get its local DNS name and port, use those to create a .hostPort(…) endpoint, a