“A Summary of the WWDC25 Group Lab”

Hello, Thanks for your response and for pointing me to TN3186. I have carefully followed the troubleshooting steps, but the issue still persists. Below is a detailed summary of the current situation. Configuration status: The auto-renewable subscription is fully created in App Store Connect Product ID: sylvoy_sylvoy_premium_v2_monthly Status: “Ready to Submit” Pricing is configured and available across regions The subscription is correctly added to the app version under “In-App Purchases and Subscriptions” StoreKit is properly implemented and getSubscriptions is called with the correct product ID Testing performed: Tested on a physical device (not simulator) Logged in with a Sandbox Apple ID Logged out and re-authenticated the App Store account Reinstalled the app multiple times Waited for propagation delays (over 24 hours) Verified that no StoreKit errors are returned (only an empty product array) Confirmed that bundle ID and product ID match exactly Current behavior: getSubscriptions() always retur

Let me start by saying two slightly contradictory things: It's very likely that there is an APFS bug here, so if you haven't already, please file a bug on this and post the bug number back here. It's ALSO very likely that your ES client (possibly both ES clients) are required to actually experience this bug, and you should address it as well. Next, I think I want to be clear that some of what I'm saying is a bit of an educated guess. A big part of the problem here is that the data we're looking at is being collected LONG (2+ days) after the problem itself actually occurred, which means we don't REALLY know EXACTLY what happened. That doesn't invalidate what I'm describing above, but I do think it's important to have some awareness of the limitation of the data at hand and that, most importantly, new data could totally change our understanding of the overall state of things. Getting into the details: But here, I don't see such things. When EndpointSecurityEventManager is on the spindump, it's only because they

All apps should build with the latest SDK, so you have access to the latest APIs, regardless of the distribution mechanism used. Regarding the UIDesignRequiresCompatibility questions, it's useful to see how this was described in the WWDC25 Platforms State of the Union: As you evaluate your app's UI and the time you need to adopt the new design, we're providing an option to continue to use your app's current design with Xcode 26. We intend this option to be removed in the next major release. Hopefully you're on your way with the adoption of the new design already, or have upcoming plans to tackle it. You'll have to look at your own specific situations and determine how long you can continue using it for specific hot fix situations against the above statements and the timing of your own planned adoption of the new design. What are the potential issues if a team continues development on Xcode 16 while others have migrated to Xcode 26? For example, could there be compatibility, build, or integration chal

@h2oconsulting I can't test it in the sandbox, since the application is not approved. Testing In-App Purchase in the Apple sandbox environment doesn’t require you submit your In-App Purchases for review. For more information, see TN3186: Troubleshooting In-App Purchases availability in the sandbox. When submitting an In-App Purchase or subscription for the first time, you must submit it with a new app version. If there are multiple In-App Purchases or subscriptions related to that version, submit all of them together. Once App Review approves one or more In-App Purchases or subscriptions for your app, you can submit more In-App Purchases or subscriptions without a new app version. For more information about submitting In-App Purchases, see Submit an In-App Purchase. After submitting your In-App Purchases to App Review, they might also be missing or unresponsive during review. The sandbox environment is a test environment for testing the In-App Purchase implementation in your app with real product data from Ap

OK, here’s a summary, sorted by version: Version | User ------- | ---- 4.0.0.0.1.1762585687 | kthchew 4.0.0.0.1.1762585687 | nathan-pierce-veertu 4.0.0.0.1.1772003596 | eskimo As you can see, I’m on the latest. And this is indeed the version of the MobileDevice package inside Xcode 26.4 [1]. Consider: % plutil -extract CFBundleShortVersionString raw /Applications/Xcode.app/Contents/Info.plist 26.4 % xar -xf /Applications/Xcode.app/Contents/Resources/Packages/MobileDevice.pkg % cat PackageInfo … Earlier I wrote: [quote='880808022, DTS Engineer, /thread/819456?answerId=880808022#880808022'] When I wrote the above I hadn’t yet installed Xcode 26.4rc. So I installed that and repeated the test. [/quote] I don’t think that had an effect because I’d installed an earlier release of the Xcode 26.4 beta, one that had the same MobileDevice installer version. So I was on the latest MobileDevice prior to running my test, and updating to Xcode 26.4rc didn’t change that. So my understanding of how this should wo

❯ pkgutil --pkg-info-plist com.apple.pkg.MobileDevice groups com.apple.findsystemfiles install-location Library/Apple/ install-time 1772135996 pkg-version 4.0.0.0.1.1762585687 pkgid com.apple.pkg.MobileDevice receipt-plist-version 1 volume / I can't reply in the thread above as a comment due to limited text amount.

On my macOS 15.7.4 machine: $ pkgutil --pkg-info-plist com.apple.pkg.MobileDevice groups com.apple.findsystemfiles install-location Library/Apple/ install-time 1771452321 pkg-version 4.0.0.0.1.1762585687 pkgid com.apple.pkg.MobileDevice receipt-plist-version 1 volume /