Search results for

A Summary of the WWDC25 Group Lab

10,365 results found

Post

Replies

Boosts

Views

Activity

Reply to Building macOS apps with Xcode 26 on macOS 26 VM
So, the tl;dr here is that this issue is now resolved. There may be other outstanding issues, but you can now: On a macOS 15 or later host, install macOS 15 or later in a VM. On the guest, log in using an Apple Account in System Settings. And install Xcode. And add your Apple Account to Xcode. And then build and run a Mac app. Even if it uses a restricted entitlement. If you’re interested in how I tested the above, I’ve included a summary at the end of this post. If you’re encountering other issues, please start a new thread with the details. This thread is already long enough |-: If you’re interested in the history, I have a summary of that in this post. That was from 13 Jun 2025. Since then there’s been one critical change, namely that on 9 Oct 2025 we rolled out a Developer website update that fixes the provisioning UDID issue (r. 149209127). And on that note, I think I can finally put this issue to bed. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEma
Oct ’25
Reply to macOS App Groups / transition to profile based groups
You are indeed confused (-: You use the term profile based app group, which is problematic. As of Jun 2025, the Developer website issues Mac provisioning profiles that authorise the use of both iOS- and macOS-style app group IDs. So the phrase profile based app group doesn’t really mean anything. That’s why I use the terms iOS-style app group ID and macOS-style style app group ID. If you have an existing app that uses a macOS-style app group ID then: Switching to an iOS-style app group ID is a lot of work. And it has very few benefits [1]. Given that, I recommend that you not switch unless there’s a compelling reason to do so. OTOH, if you’re starting from scratch then I recommend that you use an iOS-style app group ID. It’s most definitely the future. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] One of the few benefits I can think of is that it allows you to shar
Topic: App & System Services SubTopic: Core OS Tags:
Oct ’25
macOS App Groups / transition to profile based groups
Hi, I have a macOS app distributed through the App Store that uses an app group to share data with app extensions. The group identifier has the form: .group. In Xcode 26 I am now asked to convert the project to profile based app groups (like on iOS). My question is: Can I convert the project to profile based app groups and will the existing app group (which is prefixed with the Team ID) continue to work (and will exiting users still be able to access their data). If yes, should I add the app group with or without the Team ID prefix to the profile.
3
0
188
Oct ’25
Use two NFC entitlement in the same App
Hello, I have developed an iOS application called DinecTag (be.dinec.DinecTag) with a developer account named Dinec International which is registered in Belgium, I received the NFC entitlement valid for Europe and my App is on the App store since some months (the App is used to open doors by presenting the iPhone in front of a special reader) The App is published only on countries inside Europe (it don’t work outside anyway) I would like my App can be used outside Europe, so I need another entitlement called NFC & SE Platform entitlementn to ask for that, I need an account registered in a country covered by that entitlement Dinec is a company that is member of the Lisam group Lisam has an apple developer account registered to USA, called Lisam Systems So I have asked to the owner of that account to add me as a developer in the USA team So when I connect to my developer account, I can switch between Dinec International SA and Lisam Systems on top right of the screen, I am member of the two teams.
1
0
124
Oct ’25
Customizable Toolbar on iPadOS26 seems not customizable
Hi, I have started app development fairly recently and I decided to develop for Apple due to the fact that my school uses iPads and they were so convincing that I decided to buy more Apple products adding to the experience with the iPad such as a Mac where I learned Xcode, Swift and SwiftUI as far as I could comprehend. I am working on a document based app for my school and I want to implement a toolbar that’s user customizable. There seems to be no way to get a customizable toolbar running on iPadOS26 though iPadOS16 has supported this feature and it has been till 18, I believe. I have set up a doc-based app in Xcode and that and all of its views do work except the toolbar that I added to my NavigationSplitView. The items show, when their defaultCustomization isn’t set to .hidden. The toolbar is given an id and the items are all wrapped in the ToolbarItem structure that also is given an id and the placement of .secondaryAction. The items show up and behave as expected in terms of grouping and making
1
0
153
Oct ’25
Why is CoreNFC unavailable from App Extensions (appex)? Any supported workarounds for authenticators?
Hi everyone — I’m developing an iOS passkey/password manager where the private key material must be stored on a physical device (NFC card / USB token). I’m hitting a hard limitation: CoreNFC is not available for use from app extensions, which prevents an appex (e.g. password/credential provider or other extension) from talking directly to an NFC card during an authentication flow.  My questions: 1. Is there any plan to make CoreNFC (or some limited NFC-API) available to app extensions in a future iOS version? If not, could Apple clarify why (security/entitlements/architecture reasons)? 2. Are there any recommended/approved workarounds for a passkey manager extension that needs to access a physical NFC token during authentication? (For example: background tag reading that launches the containing app, or some entitlement for secure NFC card sessions.) I’ve read about background tag reading, but that seems to be about system/OS handling of tags rather than giving extensions direct NFC access.  3. Is the only s
1
0
148
Oct ’25
Reply to App Group Not working as intended after updating to macOS 15 beta.
[quote='861637022, Macho Man Randy Savage, /thread/758375?answerId=861637022#861637022, /profile/Macho+Man+Randy+Savage'] I'd like to know what the recommendation is for a new Mac app. [/quote] App Groups: macOS vs iOS: Working Towards Harmony is quite clear about this: If you’re writing new code that uses app groups, use an iOS-style app group ID. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Privacy & Security SubTopic: General Tags:
Oct ’25
App Group Not working as intended after updating to macOS 15 beta.
I have an app (currently not released on App Store) which runs on both iOS and macOS. The app has widgets for both iOS and macOS which uses user preference (set in app) into account while showing data. Before upgrading to macOS 15 (until Sonoma) widgets were working fine and app was launching correctly, but after upgrading to macOS 15 Sequoia, every time I launch the app it give popup saying '“Kontest” would like to access data from other apps. Keeping app data separate makes it easier to manage your privacy and security.' and also widgets do not get user preferences and throw the same type of error on Console application when using logging. My App group for both iOS and macOS is 'group.com.xxxxxx.yyyyy'. I am calling it as 'UserDefaults(suiteName: Constants.userDefaultsGroupID)!.bool(forKey: shouldFetchAllEventsFromCalendar)'. Can anyone tell, what am I doing wrong here?
26
0
4.9k
Oct ’25
Reply to macOS App Groups / transition to profile based groups
If you have existing users without data stored in an app group container that uses a macOS-style app group ID, you should continue to use that macOS-style group ID. There’s no mechanism to, say, move content from that app app group container to a different app group container associated with an iOS-style app group ID. The good news is that, as of Jun 2025, these macOS-style app group IDs are authorised by your provisioning profile, which avoids a number of headaches. App Groups: macOS vs iOS: Working Towards Harmony has the details. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Core OS Tags:
Oct ’25
Reply to How to keep API requests running in background using URLSession in Swift?
IMO it’s best to classify your requests into two groups: Small, interactive requests Large transfers Use a background session for the latter. The system will then continue to process the request even if your app is suspended in the background. Use a standard session for your small, interactive requests. You then have two options: Cancel any outstanding request as the app moves to the background. Use a UIApplication background task to prevent your app from being suspended in the background while the request is in flight. See UIApplication Background Task Notes for more info about that last bit. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Oct ’25
422 error "Beta contract is missing" Testflight
I'm currently experiencing the same problem that many have had with error 422 Beta contract is missing. I read that I should contact Apple support, but when I try to access the support page and log in with my credentials, the page doesn't load and I can't generate a ticket to resolve this problem. I get the message There was an error processing your request. Please try again later. And when I inspect with Safari it shows me this information: errors : [ { id : 9be0314c-3bd5-4143-a625-602322d7156e, status : 422, code : ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING, title : Beta contract is missing for the app., detail : Beta Contract is missing. } ] This is when I want to share the most recent build of my app with external groups through Testflight, but additionally, when my internal testers try to access it through Testflight app, it shows the error The requested app is not available or doesn't exist. Could someone tell me what process I should follow or where I can correctly generate the ticket for my e
1
0
789
Oct ’25
DriverKit DEXT Logs Only Once, Subsequent Logs Are Lost Despite Normal Functionality
Hello everyone, I've encountered a very strange and persistent logging issue with my DriverKit DEXT and would appreciate any insights from the community. [Problem Summary] My DriverKit DEXT, along with its companion Swift app, is functionally working perfectly. I can repeatedly call methods in the DEXT from the app (e.g., a Ping-Pong test and a StaticProcessInbandTask call) and receive the correct response every time. However, the os_log messages within my IOUserClient subclass are only successfully recorded for the very first set of interactions. After that, all subsequent logs are completely missing. What's even stranger is that all successfully recorded logs are attributed to the kernel: process, even for purely user-space methods like ExternalMethod. [Development Environment] macOS: 15.7.1 Xcode: 16.4 Hardware: MacBook Pro M1 DEXT Logging Macro (Log.h): #include #define Log(fmt, ...) do { os_log(OS_LOG_DEFAULT, [%{public}s] fmt, __FUNCTION__, ##__VA_ARGS__); } while (0) [Steps to Reproduce &
3
0
182
Oct ’25
Reply to DriverKit DEXT Logs Only Once, Subsequent Logs Are Lost Despite Normal Functionality
Hi Kevin, Thank you for your reply. It gave us a clearer understanding of how the DEXT Log mechanism works. You were right: the logs were indeed always there; our filtering methods were just missing them. Here is a summary of how we solved the silent log issue: We tried using sysdiagnose. However, for our specific need to capture IOUserClient interaction logs in real-time, the amount of data in the report was too large to be effectively analyzed. The core of the problem was that our DEXT generates a continuous and massive amount of logs, which drowned out the logs from the UserClient methods. Therefore, we created a new, dedicated logging macro, uLog(), for the exclusive use of our UserClient. Next, we modified Log.h to add a compile-time switch (#ifdef), which allows us to completely compile-out the Log() macro from the core engine at compile time, leaving only the new uLog(). All the noise from the DEXT disappeared, and the logs from ExternalMethod appeared clearly and reliably. We have now switche
Topic: App & System Services SubTopic: Drivers Tags:
Oct ’25