A Summary of the WWDC25 Group Lab

Had a discussion with the build systems team at WWDC25 about this. The reason they gave that we can not differentiate the preview build from regular builds, is that they are practically the same. They use the same build process, caches, etc. so there is no meaningful way to distinguish them. The recommended solution here is to avoid changing files during the build if at all possible. For example, a formatter should be run with auto-correction disabled during build phase scripts. One way to achieve auto-correction would be to leverage git-hooks to run the formatter before your code is pushed.

The issue does not appear to be with the first tab, but with navigation title and navigation stack in a set of views in a TabView (iOS) or NavigationSplitView (iPadOS). I've added the following new content to the feedback issue: ⸻ SwiftUI .navigationTitle Bug Diagnosis — iOS/iPadOS 26.0 Issue Summary • The navigation title set using .navigationTitle(Directives) in DirectivesView fails to appear on iOS/iPadOS 26.0, even when following Apple’s current SwiftUI best practices. • The same code works as expected in earlier versions (e.g., iOS/iPadOS 18.5). • The issue persists for both iPhone and iPad targets. Diagnostic Steps Taken Modifier Placement and View Structure • Tested both attaching .navigationTitle and a .toolbar (with a visible button) directly to the immediate child of NavigationStack (ZStack), and to the NavigationStack itself. • No change: Navigation bar, title, and toolbar item remain absent in iOS/iPadOS 26.0. Content Minimization Test • Replaced the entire content of DirectivesView with

@Quappi, I do not have an answer, however, because the type is a HKCategoryType and the frequency of the data being saved should be low, it would be reasonable to assume that .immediate would behave the way you expect--immediate when on device. I seem to recall the behaviors of some of the quantity samples are these buckets as you have described: immediate 10-minute hourly daily weekly I don't remember if the 10-minute bit was knowledge from a WWDC lab, or trial and error experimentation with workout APIs. Ever notice how Apple Watch will ask you if you're working out roughly after 10 minutes of walking?... HKQuantityTypes have an aggregation style property, there is no reason that health types couldn't have a property to represent the fastest allowed background update frequency. FB18604790 - HealthKit: Create new API for developers to check the minimum allowed update frequency for background updates, or robust documentation per-sample type #feedbackfriday

The new Liquid Glass APIs are certainly not SwiftUI-only. They are available in UIKit and AppKit. You should use UIGlassContainerEffect to get the effects of morphing and grouping. [Documentation] When using UIGlassContainerEffect with a UIVisualEffectView you can add individual glass elements to the visual effect view's contentView by nesting UIVisualEffectViews configured with UIGlassEffect. In that configuration, the glass container will render all glass elements in one combined view, behind the visual effect view's contentView.

(Continued) Are there best practices for taking an existing swiftUI app and making a two dimentional visionOS app? Compatible iOS apps can run on visionOS, see Making your existing app compatible with visionOS. If you want to go further than compatibility, you can add visionOS as a platform to your Xcode project’s target, and develop with the visionOS Simulator. Principles of spatial design, Design for spatial user interfaces, Design hover interactions for visionOS, and Bringing your existing apps to visionOS will provide you with lots of best practices to apply! I’m aware that baked lighting is often recommended, but is there a supported way to use dynamic lights and shadows on Apple Vision Pro—especially when working natively with RealityKit or Reality Composer Pro? If so, what are the limitations or best practices? RealityKit offers dynamic lights with shadows, limited to 8 dynamic lights at a time in a scene. You can use ShaderGraph to combine baked lighting and RealityKit’s dynamic lights, reference Peti

I have submitted multiple requests to Apple Developer Technical Support (DTS) over the past two months, clearly explaining our use case and referencing the official documentation as well as the above forum thread. I dug into this a bit and found two requests, one from you on 4/27/25 (replied to on 4/29/25) and one from a similarly named company on 6/18/25 (replied to on 6/30/25). Both received the same standard reply we send for that request, which asks a series of questions (A-> E) necessary for us to properly grant the entitlement. Unfortunately, I have either received no response or responses that do not address my request for the special entitlement. What response did you receive? The standard response we replied to both of these requests with opens with this: I’m responding to your request for access to the com.apple.managed.vpn.shared keychain access group. Before we start, I want to clarify one thing. As of Nov 2016, it’s possible for any developer to enable the Network Extension provider e

Thanks @BabyJ. I have updated my code to address the discrepancy which you've noted. My code now looks like this: ` let section = NSCollectionLayoutSection(group: group) let headerSize = NSCollectionLayoutSize(widthDimension: .fractionalWidth(1.0), heightDimension: .estimated(37.0)) let header = NSCollectionLayoutBoundarySupplementaryItem( layoutSize: headerSize, elementKind: ElementKind.sectionHeader.rawValue, alignment: .topLeading) section.boundarySupplementaryItems = [header] emotionFiltersDataSource.supplementaryViewProvider = { collectionView, kind, indexPath in guard let headerView = collectionView.dequeueReusableSupplementaryView( ofKind: ElementKind.sectionHeader.rawValue, withReuseIdentifier: emotionFiltersHeaderReusableView, for: indexPath ) as? EmotionFiltersHeaderView else { fatalError(Could not dequeue header view as EmotionFiltersHeaderView) } let sectionTitle = Section.allCases[indexPath.section].rawValue headerView.sectionTitleLabel.text = sectionTitle return headerView } Bu