Follow up: I had a Quick Look at the new SwiftUI WWDC25 session https://developer.apple.com/videos/play/wwdc2025/323 It seems I'm misunderstanding this API, do the enum cases .inline and .expanded refer to the accessory being in different states of compact? See attached screenshots below. I assumed "expanded" meant a larger expanded player, which would be fullscreen on an iPhone.

I've had it confirmed by Apple that this is expected behavior, Family Shared IAPs don't sync for about 15 minutes on average. Our solution will be to sync this information via our backend, but would be sweet if this wasn't needed and we could fully rely on StoreKit for this.

Hey! Thanks for the quick response, let me try to clarify. Only one purchase is available, it's a subscription that has to be activated by the Guardian. This IAP is shared via Apple Family and is required for the app to activate on the device belonging to the child. By "get notified" I mean that we're monitoring Transaction.updates on the child's device. I filed an FB as requested, here is the ID FB17605992 Sincerely, César Pinto Castillo Ambi Studio [quote='839421022, App Store Commerce Engineer, /thread/784312?answerId=839421022#839421022'] Hello! Are you relying on Ask to Buy alongside FamilyControls? https://support.apple.com/en-us/105055 Can you please confirm what you mean by "get notified"? Are you referring to App Store server notifications? Or are you monitoring Transaction.updates on child's device and not seeing the new transaction after the guardian completes the purchase? If it's the former, App Store server notifications should not be used for immediate entitlements, use Transaction.updates. If you are using Transaction.updates, and still facing the issue, please report it: https://bugreporting.apple.com/ , and post your FB# ticket number here. For more information see Implement proactive in-app purchase restore Explore Family Sharing for In-App Purchases [/quote]

I tried uninstalling and removing all Xcode installations, caches, caches etc and reinstall them. Nothing helped. I'm on macOS 15.4.1 (24E263) and am required to use Xcode 16.2. Build and run works, but if I set up a breakpoint the debugger disconnects with the following error Couldn't find the Objective-C runtime library in loaded images. My solution was to install a VM running 15.3.2 and install Xcode 16.2 in this environment. I used VirtualBuddy to install my VM, but I'm sure there are other options out there.

I got some help and now know what (unknown context at $10087af4c) means. It has nothing to do with Core Data. It occurs because the error enum I'm throwing is defined inside my class and is private. Now that I know this, I just need to see where the first case in my custom enum is thrown. This will get me close to the root issue.

@DTS Engineer We've figured out how to reproduce the bug. Sample code, video recording and instructions on how to reproduce have been submitted to feedback FB15483634 @seboslaw If you want to see how we reproduce it you can check out my mastodon post https://mastodon.social/@JagCesar/113302327859190678 Fingers crossed DTS responds with a workaround 🤞

Added our activity attributes type to the plist and I no longer get the Open on iPhone option. But it doesn't open our app on watchOS either. <key>WKSupportsLiveActivityLaunchAttributeTypes</key> <array> <string>MyAttributes</string> </array> Here's the errors I see in the Console: error 14:41:36.648880+0200 ClockFace Failed to retreive application record for bundle ID <private>: Error Domain=NSOSStatusErrorDomain Code=-10814 UserInfo={_LSLine=1767, _LSFunction=<private>} error 14:41:36.654383+0200 ClockFace [FBSSystemService][0x691f] Error handling open request for se.jagcesar.mat: <NSError: 0x14e23f40; domain: FBSOpenApplicationServiceErrorDomain; code: 4 ("InvalidRequest")> { FBSOpenApplicationRequestID = 0x691f; NSLocalizedDescription = The request to open "se.jagcesar.mat" failed.; NSUnderlyingError = <NSError: 0x14e4e8b0; domain: FBSOpenApplicationErrorDomain; code: 4 ("NotFound"); "Application info provider (FBSApplicationLibrary) returned nil for "se.jagcesar.mat"">; } error 14:41:36.654812+0200 ClockFace Error opening application: Error Domain=FBSOpenApplicationServiceErrorDomain Code=4 UserInfo={BSErrorCodeDescription=<private>, NSLocalizedDescription=<private>, NSUnderlyingError=0x14e4e8b0 {Error Domain=FBSOpenApplicationErrorDomain Code=4 UserInfo={BSErrorCodeDescription=<private>, NSLocalizedFailureReason=<private>}}, FBSOpenApplicationRequestID=<private>} It looks as if it's trying to open an app with the bundle identifier se.jagcesar.mat, but the watchOS bundle identifier is se.jagcesar.mat.watchkitapp. Afaik the watchOS bundle identifier has to use the iOS bundle identifier as a prefix followed by .watchkitapp.

I'm seeing the same as the other engineers, this is shown in the Console: error: CoreData+CloudKit: -[NSCloudKitMirroringDelegate _requestAbortedNotInitialized:](2191): <NSCloudKitMirroringDelegate: 0x28299c000> - Never successfully initialized and cannot execute request '<NSCloudKitMirroringExportRequest: 0x2835bc8c0> 5E186BF6-7A7E-49FE-9FBD-1FA163B49685' due to error: <CKError 0x281870fc0: "Partial Failure" (2/1011); "Failed to modify some records"; uuid = 279208A9-3E17-4B25-90AB-BBB4FD18ABDC; container ID = "iCloud.se.jagcesar.mat"; partial errors: { 6106D943-E708-42F9-A661-A62AE82EBA86:(com.apple.coredata.cloudkit.zone:__defaultOwner__) = <CKError 0x281871620: "Quota Exceeded" (25/2035); server message = "Quota exceeded"; op = 72544197A933D70D; uuid = 279208A9-3E17-4B25-90AB-BBB4FD18ABDC; Retry after 343.0 seconds> }> This error says Quota Exceeded: <CKError 0x281871620: "Quota Exceeded" (25/2035); But we only receive an NSPersistentCloudKitContainerEvent with CKError 2 <NSPersistentCloudKitContainerEvent: 0x2835b6a30> { type: Export store: 4D7F0616-0DB0-44DB-B68B-EE4420E66B80 started: 2024-07-25 12:22:43 +0000 ended: 2024-07-25 12:22:44 +0000 succeeded: NO error: CKErrorDomain:2 } We need to be able to inform our users that syncing isn't working because they're out of iCloud Storage.

I can still reproduce this on iOS 17.5.1. Filed a feedback with instructions how to reproduce, sample code, video recording and sysdiagnose. FB14451403

Just wanted to thank you for taking the time to write this post. An app of ours was also rejected for this reason. Are you willing to share how it later went for your app, did it ever get approved?

Ran into the same issue. Our temporary ugly fix is to merge the changes in the SPM Localizable to the main target Localizable. It's not a beautiful solution, but it works for now. Hopefully Apple folks see this and can share some insights.

Omg, thanks for sharing this @thomas_maht. I noticed this issue yesterday and have spent 4-5 hours trying to figure out why the event threshold was resetting.

Hello! Just wanted to share that the same problem occurs in 2023. 😂

I'm having seeing the same problem. App Intent executes the 'perform' block without asking the user for confirmation :( ** Edit: To clarify, we run the AppIntent from a button in a Live Activity Widget and Dynamic Island. It runs the perform block and completely ignores user confirmation in both places.

I'm still seeing this behavior in MeasurementFormatter. Did you ever get any response in your feedback issue @EinharchAltPlus?