A Summary of the WWDC25 Group Lab

Based off that, it feels like I should NOT rely on the BGContinuedProcessingTask notifications (or whatever they are called) to communicate state. It seems like instead what I should do is do something like local notifications to communicate state and handle it more in my app, is that correct? This is one of those questions where the right answer really depends ENTIRELY on the exact details of what you're trying to do. The simple end of the spectrum here are things like short-lived, single jobs, where putting up extra” UI to manage a single task which isn't going to take very long anyway might be unnecessary. At the other end of things, I think there are lots of situations where the work the app is doing doesn't nicely map directly to the task model and you'll absolutely want to use other tools/APIs to tell the user what's going on. As one example, if an app is doing lots of small network transfers, using an individual processing task for each transfer is probably a mistake. At a technical level, there are ca

I figured out that the app im developing not the sample project was causing the HealthKit service to corrupt which subsequently caused the freeze in HKLiveWorkoutBuilder. Below is the code for how i end and start workouts in my app. I cant figure out why healthkit gets corrupted. func start() async throws { guard !sessionState.isActive else { return } let configuration = HKWorkoutConfiguration() configuration.activityType = .swimming configuration.locationType = .outdoor configuration.swimmingLocationType = .openWater if extendedSession == nil { extendedSession = WKExtendedRuntimeSession() } session = try HKWorkoutSession(healthStore: store, configuration: configuration) builder = session?.associatedWorkoutBuilder() builder?.dataSource = HKLiveWorkoutDataSource(healthStore: store, workoutConfiguration: configuration) session?.delegate = self builder?.delegate = self print(💧 Submersion Manager: (manager == nil ? Unavalible : Running)) //session?.startActivity(with: .now) try await withTimeout(for: .seconds(10

Hi Apple team, Thanks for the follow up. Here are the details you requested: Platform: iOS (running on iPhone hardware; built with Xcode 15, iOS 17 SDK). Extension type: Network Extension provider packaged as an app extension (appex) within the main app target. Keychain configuration: The main app and the extension both have the Keychain Sharing capability enabled with the same access group (for example, ABCD1234.com.example.shared). We also tried the common app group and specifying the access group via kSecAttrAccessGroup, including variations such as $AppIdentifier.KeyChainSharingGroup. Error observed: When the extension attempts to access the shared keychain, SecItemCopyMatching returns status 25291 (errSecNotAvailable), which Xcode reports as No keychain is available. The same code and access group work from the containing app. Could you advise whether additional entitlements are needed for Network Extension providers on iOS, or if there are specific packaging or provis

This alert is part of the app group container protection feature. For more background, see: The WWDC video I linked to in Trusted Execution Resources App Groups: macOS vs iOS: Working Towards Harmony [quote='808931021, Ankita13188, /thread/808931, /profile/Ankita13188'] I am attempting to read and write data to an Office Group Container [/quote] I don’t understand “Office Group Container”. Is this a container for an app group from some other third-party developer? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I team! Do we have any updates regarding this? We've installed the last version of the Transporter APP available from the official site and checked the documentation (https://help.apple.com/itc/transporteruserguide/en.lproj/static.html). But seems very outdated regarding the last changes performed with Apple Connect API authentication. Many of companies that work with hybrid platforms (highcode/lowcode) doesn't have any MacOS systems with Transporter app, that allow deliver ipa files to Apple Store Connect (for test or production). It would be important to cover this scenarios. We already tried some commands, but seems that somethink is still missing. Executing comands like this ones always retrieved errors: iTMSTransporter.cmd -upload -assetFile .mobile-appapp.ipa -apiKey -apiIssuer -sigingKey -v eXtreme -assetDescription [2025-12-02 15:34:24 WET] DEBUG: Setting System property: DataCenters = contentdelivery02.itunes.apple.com [2025-12-02 15:34:24 WET] DEBUG: Setting System property: DataCenters.host = con

The canonically correct way to manage Mach service names [1] in a sandboxed app is to make the name a ‘child’ of an app group ID. That’s what I recommend that you do here. Temporary exception entitlements are a reasonable option when: You’re not targeting the Mac App Store No other option is available to you I talk more about that in The Case for Sandboxing a Directly Distributed App. But in this case you are targeting the Mac App Store and there is a better option available, and hence my recommendation. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] This includes XPC named endpoints. I recommend that folks not use Mach directly, although I realise that’s not something under your control here.

If you have multiple issues, it’s generally best to put them in different threads. That’s because different folks have different expertise, and it’s unlikely that any one person will be able to help you with all of your issues at once. In this case, I can address your second question: [quote='808920021, chps67, /thread/808920, /profile/chps67'] In Xcode 16 why is it no longer possible to arrange my files as I did before [/quote] I’m not 100% sure I understand this, but I suspect it’s because Xcode now has two ways to organise items in the Project navigator: Groups, as used by older versions of Xcode Folders, which are new [1] With groups you can explicitly manage the position and order of items in the Project navigator. With folders, Xcode does that implicitly, replicating the file system hierarchy and showing all the items alphabetically. Folders have some really important advantages — most notably, they radically reduce the number of project file merge conflicts — but if you don’t like the

Well, that's your opinion. I've managed to release a number of Swift apps without seeing the issues you describe. I've got no idea why you can't organise your folders properly. What's the problem? You ask why it's no longer possible to do something, but you haven't really explained what it is that you're missing. You can still right-click a file or folder and create a new group, new group from selection, new folder, and new folder from selection. And you can drag files and folders onto the Project pane and choose how they're added. I don't understand what it is that you're having a problem with? Rather than posting here, why not raise feedback tickets and explain where you're seeing issues? Give Apple a record of the problems and a chance to fix them. You can do that at: https://feedbackassistant.apple.com/ then post the FB number(s) here. Also, Xcode 26 is out, so you could try that out and see if any of your issues are fixed.