A Summary of the WWDC25 Group Lab

OK, so definitely not your project. If you temporarily remove the iCloud key-value storage capability capability, the app builds, right? If so, look in the build log for an entry like this: CodeSign …/Test811382.app (in target 'Test811382' from project 'Test811382') cd …/Test811382 Signing Identity: Apple Development: Quinn Quinn (7XFU7D52S4) Provisioning Profile: iOS Team Provisioning Profile: com.example.apple-samplecode.Test811382 (5db3ba83-07fb-4780-8ca4-f87de64fd20d) Note For info on how to get the build log, see Command [something] failed with a nonzero exit code. The UUID in that entry is the UUID of the provisioning profile that Xcode is using to sign your app. You should find that in ~/Library/Developer/Xcode/UserData/Provisioning Profiles. Now dump the contents of that profile like so: % security cms -D -i 5db3ba83-07fb-4780-8ca4-f87de64fd20d.mobileprovision | plutil -p - { … Entitlements => { application-identifier => SKMME9E2Y8.com.example.apple-samplecode.Test811382 com.apple.developer.iclo

There are two options available to third-party developers here: Sandboxed app containers — These are protected as of macOS 14. App group containers — These are protected as of macOS 15. I have links to the WWDC sessions that introduce these protections in Trusted Execution Resources. Neither of these is as tightly locked down as you’d like, but such is the nature of security trade-offs. And many of the MAC protected directories for Apple products, like ~/Library/Mail, have similar trade-offs, with ways around the protection like Full Disk Access or the Finder. And this is the Mac, so if the user turns off SIP then all bets are off. IMPORTANT If you do anything with app groups on the Mac, see App Groups: macOS vs iOS: Working Towards Harmony. [quote='872297022, SpacedCowboy, /thread/812688?answerId=872297022#872297022, /profile/SpacedCowboy'] where do you keep the master encryption key [/quote] My standard answer to that is the data protection keychain. That’s protected by the Mac’s

A local support person from the company says that my subscription plans are ready for submission even though the status for both localization options are Prepare for Submission. He or she says the following is written somewhere although I don't see it. You uploaded all the metadata needed, but you have not yet sent it to Apple for review. He or she says that the Prepare for Submission status for the localization options only suggests that the subscription group isn't submitted for the review and isn't approved. That's a terribly bad design.

Hi Kevin, Thank you for your detailed feedback and for spending time looking at your internal driver implementation. I have followed your suggestions and filed a formal bug report. 1. Bug Report Filed I have filed a bug report via Feedback Assistant. Feedback ID: FB21636775 I have attached the original and symbolicated crash logs, along with reduced code snippets showing our implementation. 2. OSAction Pointer Confirmation I have verified the value of the completion pointer received in UserProcessBundledParallelTasks. As you suspected, the pointer address is identical for all commands within a single bundle. 3. Crash Log Insights The symbolicated crash log confirms that the panic is triggered by an __assert_rtn inside OSMetaClassBase::QueueForObject during the call to completion. Specifically, when we attempted the Unified Path (using legacy ParallelTaskCompletion for bundled commands) as a stability test, it triggered an immediate panic, which confirms your point that we MUST use BundledParallelTaskCompletio

Two things: These are the Developer Forums, where developers of third-party apps for Apple's platforms ask each other for hints and tips on coding. You're talking to random third-party developers from around the world, not Apple's developers; If you have a suggestion, you should raise it at: https://www.apple.com/feedback/ but please note that your post doesn't really explain the issue, so please clearly state what's wrong with the three dots button. There is no option in that menu to directly delete a tab group; it's more than one tap away - so whatever you're doing it's not as a direct result of that menu.

@DTS Engineer I also don't think it's anything to do with my code (though I could always be wrong). This pipeline ran for 1hr 33min until I canceled it and none of the 3 targets finished, they all got stuck at 93%: https://appstoreconnect.apple.com/teams/411a63c1-9d73-4245-8bec-d755e3579ec7/apps/6737959724/ci/builds/ac32a2f1-0a28-446b-bae1-c3228612af8b/summary This pipeline ran for 53 minutes until I canceled it but iOS target succeeded, macOS and visionOS were stuck at 93%. https://appstoreconnect.apple.com/teams/411a63c1-9d73-4245-8bec-d755e3579ec7/apps/6737959724/ci/builds/3cb93c56-2eb4-4984-97df-879c0e83c8dd/summary BOTH of these pipeline runs were for the same exact commit, the code didnt change between them yet in one of them iOS succeeded and in the other one it didnt.

@DTS Engineer yes I submitted a request but it was through the contact us form not through feedback assistant: https://developer.apple.com/contact/case/102801901445/solution/select Case 102801901445 As far as sharing the project, here's a direct link to the pipeline: https://appstoreconnect.apple.com/teams/411a63c1-9d73-4245-8bec-d755e3579ec7/apps/6737959724/ci/builds/28aadaf4-68e2-4e10-9a18-fd69a574307d/summary

Now the problem. When the application was initially in the foreground and has an established server connection, we initially keep the server connection active when the app enters the background state, until a certain timeout or the system decides our app needs to be killed/removed from memory. This allows us to finish an incoming audio stream, quickly react on incoming responses, etc. When we then receive an incoming audio stream after a certain delay (for example, 5 seconds), we call the channelManager.setRemoteParticipant method (using try await syntax). So, the short summary is that this should just work. More specifically, all PTT apps are allowed to initiate playback at any time by calling setRemoteParticipant(), even if they're in the background. In particular, what you're describing here: we initially keep the server connection active when the app enters the background state, until a certain timeout or the system decides our app needs to be killed/removed from memory. ...is actually pretty com