The Certification Authority (CA) for Apple Push Notification service (APNs) is changing. APNs will update the server certificates in sandbox on January 20, 2025, and in production on February 24, 2025. All developers using APNs will need to update their application’s Trust Store to include the new server certificate: SHA-2 Root : USERTrust RSA Certification Authority certificate. To ensure a smooth transition and avoid push notification delivery failures, please make sure that both old and new server certificates are included in the Trust Store before the cut-off date for each of your application servers that connect to sandbox and production. At this time, you don’t need to update the APNs SSL provider certificates issued to you by Apple.

I have an iOS and watchOS app where both can run independently, I am not using WatchConnectivity to send data back and fourth. The issue I'm having is that if I schedule a local notification on the watch and the phone is unlocked, it will not show on the watch for about 10-15 seconds. If I uninstall the iOS app or have the phone locked, it will show immediately on the watch. To my understanding, this is somewhat the expected functionality but is there a way to bypass it? My app is a timer app and it really should not have a delay.

Regarding the latest news from apple below. I am not able to understand what exactly needs to be done. I can download RSA certificate from the link given but to include it in Trust store is something i am not able to get. can someone help me out here? " The Certification Authority (CA) for Apple Push Notification service (APNs) is changing. APNs will update the server certificates in sandbox on January 20, 2025, and in production on February 24, 2025. All developers using APNs will need to update their application’s Trust Store to include the new server certificate: SHA-2 Root : USERTrust RSA Certification Authority certificate. To ensure a smooth transition and avoid push notification delivery failures, please make sure that both old and new server certificates are included in the Trust Store before the cut-off date for each of your application servers that connect to sandbox and production. At this time, you don’t need to update the APNs SSL provider certificates issued to you by Apple."

Hey there, i created a independent Watch OS app and I configure push notification there. so on watch simulator I am able to get push notification every time. but today I test watch app to my real watch series 6 WatchOS 11. I got the permission alert I allowed it, and I am able to get the device token as well now if I try to send push notification to my real watch app I get this logs. Oct 22, 2024, 11:09:12.024 AM GMT+5 received by APNS Server Oct 22, 2024, 11:09:12.334 AM GMT+5 discarded as application was not registered why is that ? is there any body know's ? why i am not receiving remote notification on my real watch instead i get that my application is not register...

I am using a Key to connect my notification server with APNS in order to send out notifications to users. I have recently added notifications to a second app of mine, using the same notification server to fire off notifications for both apps. However, any notifications going to the second app return the error InvalidProviderToken, where as I get no such issues when send notifications to the first app. Everything, including the payloads, are exactly the same between the two apps, the only difference is that the device IDs are attached to different apps. Does anyone know why/how this would happen and how I can resolve it?

Over the past few weeks I've seen several people mention pushes sent via the sandbox haven't been getting delivered. Today I'm also seeing that (though pushes sent via production are fine). So it would appear to be down again. What's going on recently, any reason it's so unstable these last few weeks?

Hello, since updating (last night) to developer beta 18.2, I no longer have email count numbers / badges showing. I don’t know if others are experiencing this, but thought I should report it.

I am developing an app which makes use of actionable notifications. On my code (the func userNotificationCenter function), I need to read my users from the local storage on the iPhone: let query: [String: Any] = [ kSecAttrService as String: "uio-auth", kSecAttrAccount as String: "users", kSecClass as String: kSecClassGenericPassword, kSecReturnData as String: true ] var result: AnyObject? SecItemCopyMatching(query as CFDictionary, &result) let ref = result as? Data But when the same code execute when I tap on the notification on the Apple Watch, it doesn't fetch anything. It now occurs to to me: Does it mean that when an actionable notification programmed for the iOS is displayed on the Apple Watch, it tries to access its own storage, and not the iPhone? If so, is there a nice way to pass the values to the watchOS so that when the callback for the actionable notifications run, it has then the data it needs?

Apple Watch doesn't vibrate for notifications version: 11.1 help please

Dear all, I am seeking your assistance to finalize my registration in the Apple Developer Program. I have attempted to register multiple times using valid payment cards, but I received an email stating that my request would be processed within two business days, and that $99 would be deducted. However, two days have passed without any progress. I am unsure if the issue is related to using my friends' cards, despite their validity. In my last attempt, I provided a photo of my friend's ID card and his passport as proof of his consent for the deduction. Could the discrepancy between the cardholder's information and my registration details be the cause of the problem? Thank you.

Hi, since a while I constantly receive the warning above and there is nothing to find on my Mac (Air M2) nor by searching the web. MacOS 15.1 Anybody an idea what this app/service is all about?

Hello, I’m reaching out to gather information regarding the upcoming changes to APNs certificates that are set to be implemented in the beta at the end of January 2025. Specifically, I would like to understand the following: What will be the practical impact of these changes on apes apis ? What actually needed to be done at trust store for this changes, and how will it affect our current setup? What steps do we need to take to update the certificates on our servers? it’s crucial for us to address these changes in advance and keep our customers informed. Thank you for your help!

I’m having an issue with Firebase Cloud Messaging (FCM) where direct messages sent via the FCM token work perfectly, but notifications from Firebase Messaging Campaigns don’t reach my iOS app. Here’s what I’ve tried and confirmed so far: Setup & What’s Working: Direct Messages via FCM Token: These are received by the app without any issues. Notification Permissions: All necessary permissions are granted on the device. APNs Authentication Key: This is configured in Firebase, and the Firebase Console shows the campaign status as “Completed,” but messages don’t appear on the target device. My Steps: Uploaded the APNs Authentication Key in Firebase: Opened Apple Developer Console > Certificates, Identifiers & Profiles > Keys > Registered a New Key > Checked APNs service. Downloaded the APNs Key and uploaded it to Firebase under Project Settings > Cloud Messaging. Firebase Console Campaign Setup: Notification title and body are configured. Target set to “All Users” (for testing purposes). Message settings: sound enabled, Apple badge enabled, badge count set to 1, expiration set to 4 weeks. Code Setup (relevant parts): Using Firebase for authentication and data storage with Firestore. Configured AppDelegate for Firebase, FCM, and APNs token registration. Implemented UNUserNotificationCenterDelegate methods to show notifications when the app is in the foreground. Observed Behavior: The Firebase Console indicates the campaign is “Completed,” but the messages are not received on the device. There are no errors in the Firebase Console or my Xcode logs when sending the campaign. My AppDelegate is correctly handling the APNs token and FCM token registration. Here’s My Code Setup in AppDelegate: class AppDelegate: NSObject, UIApplicationDelegate, MessagingDelegate, UNUserNotificationCenterDelegate { func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool { FirebaseApp.configure() Messaging.messaging().delegate = self UNUserNotificationCenter.current().delegate = self UNUserNotificationCenter.current().requestAuthorization(options: [.alert, .sound, .badge]) { granted, error in if granted { print("Notification permission granted") } } application.registerForRemoteNotifications() return true } func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) { Messaging.messaging().apnsToken = deviceToken } func messaging(_ messaging: Messaging, didReceiveRegistrationToken fcmToken: String?) { print("FCM Token received: \\(String(describing: fcmToken))") } func userNotificationCenter(_ center: UNUserNotificationCenter, willPresent notification: UNNotification, withCompletionHandler completionHandler: @escaping (UNNotificationPresentationOptions) -> Void) { completionHandler([.alert, .badge, .sound]) } }

Been one week and still on requested image playground image playground will not work says I’m still requested access

When using iCloud account with push in Apple mail app. The badge number of unread email is not syncing across devices. If I read an email on my iPhone my iPad mail app badge won’t update until I click into the app and wait for the update. Is there any fix of this?

in the IOS18.1 release when using Apple Intelligence the notifications will be delayed around 10 second. Even without the notification summary turned on. It seems to be a system-wide bug, anyway to fix it or bypass it.

Ever since I updated the 18.1 I have noticed on both the Uber Driver app and Lyft Driver app that the banner notifications are on a three second delay when a ride notification comes in. These banner notifications have previously shown up immediately when a ride comes in and now it’s anywhere from 3 to 5 seconds before you see them.

Hello! I am working on an app that requires to send a local push notification to the user from an app extension (from the ShieldActionDelegate to be precise). This is suggested by DTS as a workaround for this issue: https://forums.developer.apple.com/forums/thread/766644 But now, on the iOS 18.2 beta, local push notifications are delayed by up to 10 seconds, even though the push notification is classified as .timeSensitive, leading to a very bad user experience (where to user has to sit and wait for the notification to arrive without knowing how long it will take). This only happens when Apple Intelligence is turned on. This had happened previously on the iOS 18.1 beta but was fixed for the final release: https://forums.developer.apple.com/forums/thread/764848 But now the issue came back on the latest iOS 18.2 beta. I have documented the new behavior in FB15668616 Any help is appreciated!

token：1ac0f5ef2d37a0593f09e88be0f87daca27f23d4f7637fbc7a8102413d673bc3 msgId: 37d28693-16fe-0746-733e-a49d5879becc send time: 2024-11-04 22:04:18.0(UTC+08:00) response result: InternalServerError 这个是什么原因呢？

token：1ac0f5ef2d37a0593f09e88be0f87daca27f23d4f7637fbc7a8102413d673bc3 msgId: 37d28693-16fe-0746-733e-a49d5879becc send time: 2024-11-04 22:04:18.0(UTC+08:00) response result: InternalServerError 这是什么原因呢？