missing package product

Hi @DTS Engineer I would like to update our metrics for iOS 26 regarding this issue. It appears that the problem persists on iOS 26 and has worsened as the iOS 26 call count has increased. We will keep eyes on our metrics and post update here. Has there been any specific change on iOS 26? We start to implement your recommended solution, but we still need time to release it to our production environment.

What is the correct way of nudging the undo mechanism so that autosaving would see the document as dirty? Yeah, I think this is the key in this conversation, and am glad that you brought it up. There are two options to tell AppKit the document is dirty: Supporting undo / redo by using NSDocument.undoManager. This way, every change goes to the undo stack, and NSDocument knowns the change from there. Updating the change count explicitly by calling updateChangeCount(_:). The code example I provided above uses option 2 to demonstrate the idea. Your real-world app uses option 1, which is appropriate because it supports undo. Using NSTextView adds another complexity because NSTextView supports undo as well. By default, NSTextView and NSDocument share the same undo manager that AppKit provides. In this case, however, it seems that the change in your text view doesn't always lead to a dirty document – I am guessing this is why the issue happens. You can provide NSTextView a custom undo manager via NSTextViewDelegate.

Hello - Please file a Feedback Assistant ticket at https://feedbackassistant.apple.com/ and include the following: App name and app ID Product ID(s) Transaction ID(s) How you received the separate pieces of info with distinct SignedDate values? App Store Server Notification, App Store Server API response, StoreKit directly in-app, etc.? If App Store Server Notifications, and you have the complete decoded payloads for transactions in questions, please include those in the Feedback ticket as well. For more information about Feedback Assistant, please visit https://developer.apple.com/bug-reporting/. Once you have filed the Feedback Assistant ticket, please reply to this Developer Forums thread with the Feedback Assistant ID (e.g. FB########) and/or link (e.g. https://feedbackassistant.apple.com/feedback/########), and our teams will take a look. Thank you.

I don't know why, but my answer is always missing. Here is the Feedback ID FB20345124

CloudKit Push Notifications Not Delivering - Extensive Debugging Completed Issue Summary CloudKit subscriptions are properly configured and triggering, but push notifications are never delivered to devices. After extensive debugging, I've isolated the issue to CloudKit→APNS delivery failure. Environment Xcode: 15.x iOS Target: 17.0+ watchOS Target: 10.0+ CloudKit Database: Both Public and Private Testing Devices: iPhone 15 Pro, Apple Watch Series 9 Environments Tested: Development and Production What's Working ✅ 1. CloudKit Subscriptions All 6 subscription types successfully created and visible in CloudKit Dashboard Subscriptions persist across app launches (verified in dashboard) Subscription predicates correctly configured for each record type: // Example: FriendRequest subscription NSPredicate(format: toUser == %@, userRecordID) // Example: Challenge subscription NSPredicate(format: recipientID == %@ AND status == %@, userRecordID, pending) 2. Device Registration • App successfully requests and re

I ran into the same issue. I enrolled and got the subscription on Apple Developer app on iPhone. But after payment, the app shows account cannot be enrolled via mobile app and ask to enroll via web. I did, and I got charged again. How do I refund the subscription from app store? https://reportaproblem.apple.com/ doesn't let me refund and says I have no products eligible for refunds. Who/where do I contact to refund apple developer program double charge?

Regarding your first issue, I asked about that internally. It seems that there’s been a delay with it at our end. I’m hoping that we can clear that soon. I’ve sent a reminder to check on this around the middle of next week. Regarding your submission issue, your bug (FB19582905) kinda got lost )-: [1] However, App Store Connect is now accepting iOS 26 SDK uploads, so it’s possible that this has just fixed itself. Please try uploading again and reply back here with your results. IMPORTANT Don’t pass that build on to App Review, because it won’t work for them until we resolve the first issue. However, you should still be able to upload to App Store Connect. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Normally I check that bugs land in the right place when I see them mentioned here on the forums, and I did that for FB19582905. However, things went wrong after I did my check )-:

Sorry, I missed part of the code. In fact, the error scenario also has a callback. I just sent a local notification and then immediately called completionHandler(). 【guard let heartType = HKObjectType.quantityType(forIdentifier: .heartRate) else { return } let query = HKObserverQuery(sampleType: heartType, predicate: nil) { query, completionHandler, error in if let error = error { logEvent(Observer 错误：(error.localizedDescription)) completionHandler() return } logEvent(【心率有变化了) MyNotificationManager.shared.sendNotification() // 发了一个本地通知 completionHandler() } healthStore.execute(query) healthStore.enableBackgroundDelivery(for: heartType, frequency: .hourly) { success, error in if success { logEvent(已启用后台心率监听) } else { logEvent(后台监听心率失败：(error?.localizedDescription ?? 未知错误)) } } 】