Notifications

RSS for tag

Learn about the technical aspects of notification delivery on device, including notification types, priorities, and notification center management.

Notifications Documentation

Posts under Notifications subtopic

Post

Replies

Boosts

Views

Activity

CarPlay notifications unsupported for Driving Task apps in iOS 18.6
I have my app configured as a Driving Task app with the entitlement and provisioning profile correctly set up. I am also requesting the ".carPlay" notification authorization option and setting up the carplay notification category with the ".allowInCarPlay" category, both without error. When testing with the iPhone and carplay simulators the user notifications I send are appearing on the phone but not in carplay. When I check the notification settings with UNUserNotificationCenter.current().getNotificationSettings() I see that carplay is shown to be not supported ("carPlaySetting: NotSupported"). The CarPlay Developer Guide 2025-06-09 (which is the version currently referenced in the Apple docs) states that "Starting in iOS 18.4, notifications are also supported in CarPlay driving task apps". Has this discrepancy been addressed anywhere, or is this an open issue? My software versions: MacOS: Sequoia 15.6 XCode: 16.4 iPhone Simulator: iPhone 16 with iOS 18.6
3
0
737
1d
Scheduling an AlarmKit alarm from a Notification Service Extension
We have a public-safety app where a remote notification must reliably alert the user, including when the device is muted. We have requested the Critical Alerts entitlement, but until it is granted we are looking at AlarmKit. Is it supported to schedule an AlarmKit alarm (fixed date of "now" or a countdown of a few seconds) from a Notification Service Extension when a remote notification with mutable-content arrives, also when the app is not running? If not, is there a supported way to start an AlarmKit alarm in response to a remote notification without the user opening the app? Would this pattern be acceptable under the App Review Guidelines for an app whose alerts are operational requests, not marketing? Thanks!
0
0
57
1d
APNs delivery when the device has both cellular and Wi-Fi: which connection gets a pending push?
We're investigating alert pushes (priority 10, mutable-content, short expiration) that occasionally arrive 2-4 minutes late, usually around a cellular -> Wi-Fi handover. The provider gets HTTP 200 immediately. What we've observed with the APNs logging profile: apsd logs mention "dual channel is enabled" and "Connected on N interfaces", and per-interface states for WWAN and NonCellular. When we silently break the device's push connection (no RST), the device notices via a keep-alive timeout, reconnects (falling back to 443 when 5223 is blocked), and pending pushes arrive within ~0.3s of the new connection. In the field, a push sent later can arrive first: push 1 is held ~2-3 minutes while push 2, sent ~60s after it, arrives over Wi-Fi in ~2s. Questions: Can a device hold APNs connections over cellular and Wi-Fi at the same time, and if so, how does APNs choose which one to deliver a push on? If a push was sent on one connection and isn't acknowledged, does APNs keep retrying on that same connection until it times out, or does it move the push to another live connection for the same device? What is the retry/backoff behaviour for an unacknowledged push (intervals, any jitter, the timeout before it's re-queued), and does that schedule reset when the device opens a new connection? On the device side, how does apsd back off between reconnect attempts after consecutive failures, and can anything (for example network changes) cut that wait short? Anything a provider can do to reduce this (for example apns-expiration choices), or is this expected best-effort behaviour? Separate from the questions: I've been genuinely impressed by how resilient the push connection is. Even when I silently killed the connection, the device noticed, fell back to another port, and APNs delivered the pending pushes within a fraction of a second of reconnecting. It's an amazing piece of engineering and I wish I got to see behind the curtain.
1
0
61
3d
Support requested: Notification Service Extension Filtering entitlement requests blocking app updates
Hello, We’re seeking assistance with two pending Notification Service Extension Filtering Entitlement Requests, both submitted on October 27, 2026: HX7DQ5G2R4 3T2KH34RB3 The requests cover our production app and its TestFlight beta. Our production app previously had this entitlement, but after transferring it to a new Apple Developer account, we needed to request it again. Our app provides end-to-end encrypted messaging. Its notification service extension decrypts incoming content and determines whether a visible notification is appropriate. The entitlement is needed to suppress notifications for events that don’t require a user-facing alert. The full technical justification is included in our submissions. While these requests are pending, we’re unable to release updates and bug fixes to important clients who rely on the app. Could Apple staff help us check the status of these requests or direct us to the appropriate support channel? Please let us know if any additional information is needed to move the review forward. Thank you.
0
0
84
3d
Can a watchOS alarm show a custom wake screen instead of the system Open/Stop alert?
I’m developing a watchOS gentle-wake alarm using WKExtendedRuntimeSession and repeating haptics. When the app determines it is time to wake the user, I want the watch to present the app’s custom wake screen immediately. That screen includes a Stop control. The goal is for the custom screen to be the alarm experience, rather than requiring the user to tap Open on the system’s Open/Stop alert or having that system alert replace the custom screen. In hardware tests of my watchOS app (version 0.1, build 10) on November 9, 2026, I observed the system’s Open/Stop alert during the alarm. After selecting Open, the custom UI appeared, but the system alert returned after the app subsequently became inactive while the alarm session was still running. Test environment Apple Watch Series 11, watchOS 27.2 (24S118) Xcode 27.2 (27B52), watchOS 27.2 SDK Watch unlocked, Always On enabled, no attached debugger The app schedules the session with start(at:), calls notifyUser(hapticType:repeatHandler:) once, and presents a SwiftUI fullScreenCover with the wake interface and Stop button. Stop invalidates the session. In the 15-second Wake Duration test, logs showed reduced luminance after 15 seconds and inactivity about one second later. I observed the Open/Stop alert return twice after selecting Open. In the 70-second test, reduced luminance occurred 70 seconds after activation, followed by inactivity. Neither test logged a duplicate notifyUser call, process restart, or disappearance of the custom view before session termination. The logs establish lifecycle timing, but do not directly record system-alert presentation. Questions Is there a supported watchOS API or alarm architecture that can present a third-party app’s custom wake screen immediately when its alarm starts, without first showing or subsequently replacing it with the system Open/Stop alert? If so, what lifecycle, presentation, and background-haptic requirements apply, including when the app is inactive or the watch is in Always On mode? If this isn’t supported, is the system alert mandatory for WKExtendedRuntimeSession alarms, and what is the recommended alternative? Would AlarmKit with an iPhone companion change what can be presented on the watch? The custom screen would provide a clear way to stop the alarm. I’m not asking to remove the user’s ability to stop it or to keep the display at full brightness indefinitely. I also prepared a focused Watch-only sample isolating the runtime session, repeating haptics, custom presentation, and lifecycle logging. It builds successfully but has not been tested on hardware. The observations above are from the app, not the sample.
1
0
115
3d
LiveCommunicationKit: In‑call banner missing in foreground, only appears after app goes background (iPhone14 Pro)
Environment: Device: iPhone 14 Pro iOS version: 26 SDK: LiveCommunicationKit App status: Foreground / Active state Problem reproduction: Intermittent, happens on some devices, not 100% reproducible on all test devices. Expected behavior: Incoming call banner should present when app is active (foreground). Actual behavior: No system incoming‑call banner while app is foreground. Banner appears only after pressing home‑button / switching app to background. Additional notes: Our app uses LiveCommunicationKit because VoIP PushKit is not permitted for China mainland App Store distribution. Call reporting completes without error; no error returned from LiveCommunicationKit API. private func _lckReportIncomingCall(call: Call?, uuid: UUID, handle: String, hasVideo: Bool, displayName: String) { guard let manager = conversationManager else { Log.error("[ProviderDelegate-LCK] ConversationManager is nil, falling back") _fallbackReportIncomingCall(call: call, uuid: uuid, handle: handle, hasVideo: hasVideo, displayName: displayName) return } let callInfo = callInfos[uuid] let callId = callInfo?.callId ?? "" let remoteHandle = Handle(type: .generic, value: handle, displayName: displayName) let update = Conversation.Update(localMember: nil, members: [remoteHandle], activeRemoteMembers: [remoteHandle]) // 冷启动时 iOS PKPushRegistry 要求在 2 秒内上报来电,否则杀进程。 // Task { @MainActor } 是异步的,调试时主线程 RunLoop 来不及调度就超时了。 // 这里用 DispatchSemaphore 在后台线程同步等待 LCK 上报完成。 let semaphore = DispatchSemaphore(value: 0) var lckError: Error? DispatchQueue.main.async { Task { @MainActor in do { try await manager.reportNewIncomingConversation(uuid: uuid, update: update) Log.info("[ProviderDelegate-LCK] Reported incoming conversation: callId=\(callId), uuid=\(uuid)") if TelecomManager.shared.endCallkit { CoreContext.shared.doOnCoreQueue(synchronous: true) { core in let linphoneCall = core.getCallByCallid(callId: callId) if linphoneCall?.state == .PushIncomingReceived { try? linphoneCall?.terminate() } } } } catch { Log.error("[ProviderDelegate-LCK] Failed to report incoming conversation: \(error)") lckError = error } semaphore.signal() } } let waitResult = semaphore.wait(timeout: .now() + 5) if waitResult == .timedOut { Log.error("[ProviderDelegate-LCK] Timed out waiting for LCK report, falling back") _fallbackReportIncomingCall(call: call, uuid: uuid, handle: handle, hasVideo: hasVideo, displayName: displayName) } else if let error = lckError { Log.error("[ProviderDelegate-LCK] LCK report failed: \(error), declining SIP call") // 来电被拒(勿扰/黑名单等),decline 掉 SIP 侧 CoreContext.shared.doOnCoreQueue(synchronous: true) { _ in try? call?.decline(reason: .Busy) } } }
3
0
809
4d
NSE Filtering for encrypted incoming calls: what technical details should we provide?
We’re preparing the first iOS release of ANTINTWRK, an encrypted messenger with voice and video calls. Our push gateway sends a regular APNs alert for the encrypted event. On the receiving device, the Notification Service Extension fetches and decrypts the referenced event. In this delivery path, the gateway does not distinguish an encrypted call invitation from a message. When the extension identifies a ringing call, it uses CXProvider.reportNewIncomingVoIPPushPayload to hand it off to CallKit and suppresses the original alert to avoid a duplicate notification. Our Notification (NSE) Filtering request, submitted on October 25, 2026, still shows Submitted. Xcode cannot export the App Store build because the extension’s distribution profile lacks com.apple.developer.usernotifications.filtering. We have contacted Developer Support under Entitlements. We’re following Apple’s Sending End-to-End Encrypted VoIP Calls guidance. For this design, what technical details or test evidence should we provide so the capability review team can evaluate the request? Is there a recommended way to attach that material to the existing request? We can provide the request and support case IDs privately if needed.
0
0
144
6d
Apple Watch Notification Center timestamp drift on notifications processed by a Notification Service Extension
I'm seeing a timestamp display issue on Apple Watch Notification Center, and I'd like to confirm whether this is a known watchOS behavior or whether there's a setup mistake on our side. Symptom The same APNs notification displays the correct time on iPhone Notification Center and on the initial Apple Watch banner. After the Watch screen turns off and the user later opens Notification Center on Apple Watch, the same notification may show an incorrect relative timestamp such as "3 hours ago" or even "yesterday". The drift is per-notification and persists for that notification until it's dismissed. iPhone NC always shows the correct time. WhatsApp tested side-by-side on the same iPhone/Watch pair does not show this drift. Setup iOS 26.4.2 on iPhone 16 Pro watchOS 26.4 on Apple Watch Series 10 App with paired Apple Watch A UNNotificationServiceExtension that decrypts E2EE message previews and applies Communication Notification enrichment via INSendMessageIntent and content.updating(from:) Production APNs environment, TestFlight builds No beta software Isolation tests already performed Test mutable-content NSE invoked Drift on Watch NC Minimal APNs (alert + sound only) no no no drift NSE skips content.updating(from:), INInteraction.donate/delete (still calls them as no-op via diagnostic build) yes yes — modifies content drift NSE bypasses ALL Intents/Communication Notification APIs (no INPerson, no INSendMessageIntent, no avatar, no updating(from:)); just modifies title/body/sound/category and returns the mutable copy yes yes — modifies content drift Production-like APNs payload (thread-id, target-content-id, category, sound, badge, custom userInfo) but WITHOUT mutable-content no no no drift Eliminated as causes: content.updating(from:), INSendMessageIntent, INInteraction.donate, INInteraction.delete(with:), INPerson/INPersonHandle (not even constructed in test 3), avatar fetching, thread-id, target-content-id, category, sound, badge, custom userInfo, custom createdAt timestamp, stale Siri/Apple Intelligence history (cleared manually on iPhone and Watch). The pattern The only consistent variable distinguishing the no-drift cases from the drift cases is whether mutable-content: 1 is set on the APNs payload (i.e. whether the UNNotificationServiceExtension is invoked). Once invoked, the extension's behavior with respect to Communication Notifications does not seem to affect the outcome — the drift reproduces even when the NSE only modifies title/body/sound and returns. Questions Is there a known watchOS behavior where notifications processed by a UNNotificationServiceExtension use a different timestamp source on Apple Watch Notification Center after the Watch screen has been turned off and reopened, while the initial Watch banner and iPhone Notification Center show the correct delivery time? Are there specific UNMutableNotificationContent properties or APNs payload flags that should be preserved (or avoided) when returning content from an NSE to keep the Watch NC timestamp consistent with the delivery time? For E2EE messaging apps, is there a recommended pattern to decrypt and return content from an NSE that avoids this drift on watchOS? Happy to provide an anonymized snippet of NotificationService.swift and the APNs payload format if useful. Thanks.
8
0
1.8k
1w
NSE - Notification Filtering Entitlement - No Progress in Months
It's been 2+ months now since I've submitted an entitlement request for the Notification Service Filtering Entitlement (NSE). I have a mobile app that I transferred from a previous developer account due to business reorganization and the previous account had this entitlement. However, after transferring the app, I am unable to push any updates to the app on iOS because the new developer account does not have the same entitlement. Everything outside of the developer account that the app is associated to remains the same - same workflow, same audience, same app use cases, etc.. However, we still have not had any progress on receiving the entitlement even after multiple escalations and follow-ups with the Apple Developer Support team. I am curious to know if any others within the Developer Community have requested this specific entitlement before and what your experience has been with it? Any advice on how I can expedite the approval for the entitlement? Otherwise our app continues to go stale on the iOS app store.
1
1
989
1w
NSE Filtering Entitlement lost after app transfer, now blocked from shipping updates to a live app (Request ID: 3T2KH34RB3)
Hi all, Our iOS app is an end-to-end encrypted collaboration app with live customers. It was transferred to our new developer team on October 14. Before the transfer, the app had the Notification Service Extension Filtering entitlement. The entitlement did not carry over to the receiving team, and we didn't realize that until after the transfer was complete. Our pushes are end-to-end encrypted, so we can't ship a build with important updates to our customers without it. What we've done so far: Submitted the entitlement request (Request ID: 3T2KH34RB3) Opened an Apple Developer Support case on October 26 (Case #103009182658) asking for the request to be expedited Followed up by email several times and through the support form, with no response so far Our questions: Is there a process for restoring a previously approved entitlement to the receiving team after an app transfer, rather than going through a new review? Can someone confirm our request is in the review queue and share an estimated timeline? Is there anything else we can provide to help move this forward?
0
0
53
1w
APNs proper behavior when connections are reset without warning
The company I work for sends large amount of traffic to APNs on behalf of our customers, with rates up to 50k/second at peek times. While a vast majority of the messages are successful or return a proper error code that we can parse and honor, roughly 1.5 million times per day our connections are being closed without warning. The networking library we use, https://github.com/hyperium/h2, is exposing these as ErrorKind::ConnectionReset or ErrorKind::BrokenPipe. From our reading of the APNs documentation, it is unclear what the correct response is when this occurs. There is no idempotency key included with our messages, so attempting to resend the message again seems frought with the potential for double sends. However, it some cases it seems clear that at least some of the messages in flight over that connection where never sent out at all. We found this open source project unconditionally retrying messages in this case. https://github.com/rpush/rpush/pull/734 Could someone from the APNs team please lay out the expected behavior a client should have when our connection is unexpected closed in this manner?
4
1
593
1w
Keeping monitored regions in sync with server changes when background pushes aren’t delivered
Our app logs workers’ arrival and departure at work sites using CLLocationManager region monitoring (up to 20 circular regions, “Always” authorization). Each worker’s list of sites changes on our server (daily schedule, occasional same-day changes). When it changes, we send a background push (apns-push-type: background, apns-priority: 5, aps containing only content-available: 1), and the app fetches the new list and re-registers its regions. On real users’ iPhones (iOS 26.6.2) these pushes often aren’t acted on for hours. It’s typically a newly installed app the user rarely opens, sometimes swiped away, possibly in Low Power Mode. Users won’t open the app or change settings. Region monitoring itself works well for us, including relaunching the app after a swipe-away. We understand background pushes are best-effort, so we’re planning to: fetch the list whenever the app is relaunched by a region event pre-load the next work day’s sites in advance coalesce pushes (max ~2/hour per device) Questions: Is there a recommended way to keep monitored regions in sync with server-side changes for an app the user rarely opens, without user interaction or broader location tracking (we want to avoid significant-location-change for privacy reasons)? If the app is relaunched by a region event, is it fine to do a network fetch and re-register regions in that same background launch? As a fallback when a device hasn’t fetched after a change, would an alert push with mutable-content and a Notification Service Extension that downloads the new list be an acceptable use? On iOS 26, does region monitoring still relaunch an app that was swiped away from the app switcher?
0
0
81
1w
Notification filtering entitlement for an on-call pager heartbeat — none of the form's use cases fit
We build an internal on-call pager app for our engineers, distributed through TestFlight only. Our server sends a heartbeat push to each device every 4 hours. The Notification Service Extension uses it to re-arm a dead-man's-switch alarm on the device: if heartbeats stop arriving, the alarm goes off and the engineer knows the paging pipeline is down. The heartbeat has to be an alert push with mutable-content, because that is the only push type that reliably launches the extension, including when the user has swiped the app away. Background pushes don't work here: they are throttled and are not delivered to an app the user has force-quit, so the dead-man alarm would fire falsely. The problem is that every heartbeat leaves an entry in Notification Center. It carries nothing actionable, and it teaches on-call engineers to ignore notifications from a pager app. Real alerts are always shown, and the extension still shows a visible notification when a heartbeat detects a problem (missed alerts, failure to re-arm). We already send heartbeats with interruption-level passive and an apns-collapse-id, so it is a single quiet entry, but it is still there. com.apple.developer.usernotifications.filtering would solve this exactly. However, the request form requires picking one of four use cases (end-to-end encrypted messaging, earthquake warnings, education alerts, healthcare alerts), and ours is none of them. An earlier reply on this forum said other use cases are welcome to apply (https://developer.apple.com/forums/thread/676672), but the form no longer offers a way to describe one. Questions: Can an app whose use case is outside the four listed apply for the entitlement? If so, how should we fill in the required use-case field? If not, is there a supported way to have an alert push launch the extension without leaving an entry in Notification Center? For example, is it supported for the extension to remove its own delivered notification with removeDeliveredNotifications(withIdentifiers:) after calling the content handler? Thanks!
2
0
188
1w
Notifications not enabled on my app
I have set up my app to allow for notifications and had previously tested it and it was working. Now, when I or others go into settings on our phones and go to the app, notifications is not even an option. When I go into settings and go to Notifications, the app doesn't even show up in the list. As mentioned, we had previously been able to receive notifications and the Key is set up to do so. Thanks for your help!
0
0
33
1w
AlarmKit — stop automatically at the end of a custom sound while the app is suspended
We are building a scheduled-audio app. We need a complete custom recording to start at a scheduled time while the device is locked, play exactly once, and stop automatically without user interaction. The app may be suspended at the scheduled time. Environment: iPhone 11, iOS 26.6.1; Xcode 26.6 with iOS 26.5 SDK; deployment target iOS 26.1. The app was signed for development, installed, and launched without an attached debugger. Alarm authorization was granted. No background audio mode or countdown Live Activity is configured. We bundle a 154.017959-second, mono 44.1 kHz 16-bit PCM CAF in the main bundle. The recording was converted to CAF without trimming. Minimal scheduling code, called after successful authorization (using the generic example filename sample-sound.caf): import ActivityKit import AlarmKit import SwiftUI struct PlaybackMetadata: AlarmMetadata {} @MainActor func schedulePlaybackTest() async throws { let attributes = AlarmAttributes( presentation: AlarmPresentation( alert: .init(title: "Audio playback test") ), metadata: PlaybackMetadata(), tintColor: Color.teal ) let configuration = AlarmManager.AlarmConfiguration.alarm( schedule: .fixed(Date().addingTimeInterval(60)), attributes: attributes, sound: .named("sample-sound.caf") ) _ = try await AlarmManager.shared.schedule(id: UUID(), configuration: configuration) }NSAlarmKitUsageDescription is present in the built Info.plist. Reproduction: schedule, lock the phone before the fire date, then leave it locked and listen through the end. The recording starts automatically and plays completely, but then repeats. This is a single fixed alarm, not a repeating schedule. Questions: Is there a supported public configuration for playing a custom AlarmKit sound once and dismissing/stopping the alarm at end of file? If not, is there an OS-managed maximum alert duration, scheduled stop, or guaranteed callback that can meet this requirement when the app is suspended or terminated? Is unattended play-once-and-stop unsupported with the current public APIs, so that this should be filed as an enhancement request? We understand that postAlert describes a subsequent countdown, and that stop(id:) can be called by executing app code. A foreground timer or a user-triggered stop intent would not meet the requirement. We want an intended public API solution appropriate for App Store distribution.
0
0
31
2w
APNs Delivery Metrics: What Exactly Triggers “Discarded - Disabled”?
Hello, I'm trying to understand the exact meaning of the APNs delivery status Discarded - Disabled shown in Apple's Push Notification Console. According to the status tooltip: Push notifications which were discarded by APNs, because the push feature was disabled for the application on the target device. None of these were saved to APNs storage. However, I'm unable to reproduce this behavior by disabling notifications through iOS Settings. My test scenario I performed the following test on a physical iOS device: Installed our application. Enabled notifications for the application in iOS Settings. Sent a regular visible push notification (alert) from CloudKit console. Checked the individual APNs Delivery Log. The status was Delivered to Device. Disabled notifications for our application through Settings → Notifications → [Our App] → Allow Notifications. Sent another regular visible push notification using the same device token. Checked the individual APNs Delivery Log again. Unexpected result: Despite notifications being disabled in iOS Settings, APNs reported Delivered to Device, not Discarded - Disabled. I'm checking individual notification delivery records, not aggregated metrics. Questions I'd appreciate clarification on the following: What exactly does Apple mean by "the push feature was disabled for the application on the target device"? Does Discarded - Disabled refer to the notification authorization status (UNAuthorizationStatus.denied) or a different device-side state? If disabling notifications through iOS Settings does not trigger this status, what specific user action or device configuration does? Is there a distinction between disabling notification presentation and disabling remote push delivery at the APNs level? Under what exact circumstances does APNs report Discarded - Disabled instead of Delivered to Device? Additional information Push type: alert Notification type: Regular visible notification Device: iPhone 14 iOS version: 27.2 APNs environment: Sandbox My goal is to understand the exact technical conditions that produce Discarded - Disabled, rather than just the general meaning of the status. Has anyone encountered this behavior or received clarification from Apple about this particular APNs delivery status? Thanks!
0
0
106
2w
PushKit + CallKit for opt-in monitoring alerts?
Hi, Is it permitted to use PushKit and CallKit for monitoring alerts that users explicitly enable? An API event would trigger an incoming call, displaying the monitoring channel as the caller. Answering would acknowledge the alert and end the call, without establishing a voice connection. Alternatively, the app could read the alert locally using AVSpeechSynthesizer after answering. Are either of these approaches permitted, or is a network-based voice connection required?
1
0
127
2w
watchOS Standalone App Notification Settings Not Appearing
I'm having an issue on my standalone watchOS app where the settings to adjust notifications does not appear anywhere on the iPhone or the Watch. I have successfully requested notifications access from the user and have successfully displayed a local notification to them. However, if the user ever decides to revoke my notification access (or if they deny originally and want to change), the settings pane for notifications does not appear anywhere. I've looked in the following places: On the watch in Settings > Notifications, however it looks like you can no longer edit per app notification settings directly on the watch (none of the installed apps on my watch appear in here). The only options are settings like "tap to show full notification" and "announce notifications" which affect all notifications (Why not? Especially for apps that don't have a iPhone companion app?). On the iPhone in the Watch app (the app you set up your watch in), in Watch > Notification. My app does not appear anywhere in there. On the iPhone in the iPhone Settings app, in Settings > Notifications. My app does not appear anywhere in there. On the iPhone in the iPhone Settings app, in Settings > Apps. My app does not appear anywhere in there I've tried: Adding capabilities in Signing & Capabilities for Push Notification, Time-Sensitive Notifications and Communication Notifications Building the app for release instead of debug My app also requires location access and has successfully appeared in the settings pane directly on the watch in Settings > Privacy & Security > Location Services, however notification settings do not appear anywhere. I have created a stripped down test app to try and that also does not work. This test code successfully asks the user for permission and (from a button in ContentView), successfully schedules a notification and displays it to the user when they're not in the app. Here's the code for my NotificationManager: import UserNotifications class NotificationManager: NSObject, ObservableObject, UNUserNotificationCenterDelegate { static let shared = NotificationManager() @Published var hasAuthorisation = false private override init() { super.init() UNUserNotificationCenter.current().delegate = self requestAuthorisation() } func requestAuthorisation() { UNUserNotificationCenter.current().requestAuthorization(options: [.alert, .sound]) { authorised, error in DispatchQueue.main.async { if let error = error { print("Error requesting notifications: \(error.localizedDescription)") } self.hasAuthorisation = authorised } } } func scheduleNotification(title: String, body: String, timeInterval: TimeInterval) { let content = UNMutableNotificationContent() content.title = title content.body = body content.sound = .default let trigger = UNTimeIntervalNotificationTrigger(timeInterval: timeInterval, repeats: false) let request = UNNotificationRequest(identifier: UUID().uuidString, content: content, trigger: trigger) UNUserNotificationCenter.current().add(request) { error in if let error = error { print("Error scheduling notification: \(error.localizedDescription)") } else { print("Notification scheduled successfully.") } } } } This issue has persisted across two iPhones (recently upgraded) and the watch was wiped when connecting to the new iPhone. Am I missing some code? Am I missing some flag I need to set in my project somewhere? Please can someone with an Apple Watch try this code in a standalone watchOS app and see if the notifications pane appears anywhere for them? I've contacted Apple DTS, but they're taking a while to respond.
2
1
1k
2w
Please a reply , I'm loosing my mind.
hi so submitted my app 2 weeks ago , still sitting in "waiting for review" 8 emails later. .... not a single word , no relpy to tell me whats happining. As im sure eveyonr did. , we work our hearts out creating the apps , Apple please understsnd how incredibly fustrating this is, please. i begging you , please advise when i will get any communication . i apriciate you may be busy. just tell me that then please.
0
0
23
2w
CarPlay notifications unsupported for Driving Task apps in iOS 18.6
I have my app configured as a Driving Task app with the entitlement and provisioning profile correctly set up. I am also requesting the ".carPlay" notification authorization option and setting up the carplay notification category with the ".allowInCarPlay" category, both without error. When testing with the iPhone and carplay simulators the user notifications I send are appearing on the phone but not in carplay. When I check the notification settings with UNUserNotificationCenter.current().getNotificationSettings() I see that carplay is shown to be not supported ("carPlaySetting: NotSupported"). The CarPlay Developer Guide 2025-06-09 (which is the version currently referenced in the Apple docs) states that "Starting in iOS 18.4, notifications are also supported in CarPlay driving task apps". Has this discrepancy been addressed anywhere, or is this an open issue? My software versions: MacOS: Sequoia 15.6 XCode: 16.4 iPhone Simulator: iPhone 16 with iOS 18.6
Replies
3
Boosts
0
Views
737
Activity
1d
Scheduling an AlarmKit alarm from a Notification Service Extension
We have a public-safety app where a remote notification must reliably alert the user, including when the device is muted. We have requested the Critical Alerts entitlement, but until it is granted we are looking at AlarmKit. Is it supported to schedule an AlarmKit alarm (fixed date of "now" or a countdown of a few seconds) from a Notification Service Extension when a remote notification with mutable-content arrives, also when the app is not running? If not, is there a supported way to start an AlarmKit alarm in response to a remote notification without the user opening the app? Would this pattern be acceptable under the App Review Guidelines for an app whose alerts are operational requests, not marketing? Thanks!
Replies
0
Boosts
0
Views
57
Activity
1d
APNs delivery when the device has both cellular and Wi-Fi: which connection gets a pending push?
We're investigating alert pushes (priority 10, mutable-content, short expiration) that occasionally arrive 2-4 minutes late, usually around a cellular -> Wi-Fi handover. The provider gets HTTP 200 immediately. What we've observed with the APNs logging profile: apsd logs mention "dual channel is enabled" and "Connected on N interfaces", and per-interface states for WWAN and NonCellular. When we silently break the device's push connection (no RST), the device notices via a keep-alive timeout, reconnects (falling back to 443 when 5223 is blocked), and pending pushes arrive within ~0.3s of the new connection. In the field, a push sent later can arrive first: push 1 is held ~2-3 minutes while push 2, sent ~60s after it, arrives over Wi-Fi in ~2s. Questions: Can a device hold APNs connections over cellular and Wi-Fi at the same time, and if so, how does APNs choose which one to deliver a push on? If a push was sent on one connection and isn't acknowledged, does APNs keep retrying on that same connection until it times out, or does it move the push to another live connection for the same device? What is the retry/backoff behaviour for an unacknowledged push (intervals, any jitter, the timeout before it's re-queued), and does that schedule reset when the device opens a new connection? On the device side, how does apsd back off between reconnect attempts after consecutive failures, and can anything (for example network changes) cut that wait short? Anything a provider can do to reduce this (for example apns-expiration choices), or is this expected best-effort behaviour? Separate from the questions: I've been genuinely impressed by how resilient the push connection is. Even when I silently killed the connection, the device noticed, fell back to another port, and APNs delivered the pending pushes within a fraction of a second of reconnecting. It's an amazing piece of engineering and I wish I got to see behind the curtain.
Replies
1
Boosts
0
Views
61
Activity
3d
Support requested: Notification Service Extension Filtering entitlement requests blocking app updates
Hello, We’re seeking assistance with two pending Notification Service Extension Filtering Entitlement Requests, both submitted on October 27, 2026: HX7DQ5G2R4 3T2KH34RB3 The requests cover our production app and its TestFlight beta. Our production app previously had this entitlement, but after transferring it to a new Apple Developer account, we needed to request it again. Our app provides end-to-end encrypted messaging. Its notification service extension decrypts incoming content and determines whether a visible notification is appropriate. The entitlement is needed to suppress notifications for events that don’t require a user-facing alert. The full technical justification is included in our submissions. While these requests are pending, we’re unable to release updates and bug fixes to important clients who rely on the app. Could Apple staff help us check the status of these requests or direct us to the appropriate support channel? Please let us know if any additional information is needed to move the review forward. Thank you.
Replies
0
Boosts
0
Views
84
Activity
3d
Can a watchOS alarm show a custom wake screen instead of the system Open/Stop alert?
I’m developing a watchOS gentle-wake alarm using WKExtendedRuntimeSession and repeating haptics. When the app determines it is time to wake the user, I want the watch to present the app’s custom wake screen immediately. That screen includes a Stop control. The goal is for the custom screen to be the alarm experience, rather than requiring the user to tap Open on the system’s Open/Stop alert or having that system alert replace the custom screen. In hardware tests of my watchOS app (version 0.1, build 10) on November 9, 2026, I observed the system’s Open/Stop alert during the alarm. After selecting Open, the custom UI appeared, but the system alert returned after the app subsequently became inactive while the alarm session was still running. Test environment Apple Watch Series 11, watchOS 27.2 (24S118) Xcode 27.2 (27B52), watchOS 27.2 SDK Watch unlocked, Always On enabled, no attached debugger The app schedules the session with start(at:), calls notifyUser(hapticType:repeatHandler:) once, and presents a SwiftUI fullScreenCover with the wake interface and Stop button. Stop invalidates the session. In the 15-second Wake Duration test, logs showed reduced luminance after 15 seconds and inactivity about one second later. I observed the Open/Stop alert return twice after selecting Open. In the 70-second test, reduced luminance occurred 70 seconds after activation, followed by inactivity. Neither test logged a duplicate notifyUser call, process restart, or disappearance of the custom view before session termination. The logs establish lifecycle timing, but do not directly record system-alert presentation. Questions Is there a supported watchOS API or alarm architecture that can present a third-party app’s custom wake screen immediately when its alarm starts, without first showing or subsequently replacing it with the system Open/Stop alert? If so, what lifecycle, presentation, and background-haptic requirements apply, including when the app is inactive or the watch is in Always On mode? If this isn’t supported, is the system alert mandatory for WKExtendedRuntimeSession alarms, and what is the recommended alternative? Would AlarmKit with an iPhone companion change what can be presented on the watch? The custom screen would provide a clear way to stop the alarm. I’m not asking to remove the user’s ability to stop it or to keep the display at full brightness indefinitely. I also prepared a focused Watch-only sample isolating the runtime session, repeating haptics, custom presentation, and lifecycle logging. It builds successfully but has not been tested on hardware. The observations above are from the app, not the sample.
Replies
1
Boosts
0
Views
115
Activity
3d
LiveCommunicationKit: In‑call banner missing in foreground, only appears after app goes background (iPhone14 Pro)
Environment: Device: iPhone 14 Pro iOS version: 26 SDK: LiveCommunicationKit App status: Foreground / Active state Problem reproduction: Intermittent, happens on some devices, not 100% reproducible on all test devices. Expected behavior: Incoming call banner should present when app is active (foreground). Actual behavior: No system incoming‑call banner while app is foreground. Banner appears only after pressing home‑button / switching app to background. Additional notes: Our app uses LiveCommunicationKit because VoIP PushKit is not permitted for China mainland App Store distribution. Call reporting completes without error; no error returned from LiveCommunicationKit API. private func _lckReportIncomingCall(call: Call?, uuid: UUID, handle: String, hasVideo: Bool, displayName: String) { guard let manager = conversationManager else { Log.error("[ProviderDelegate-LCK] ConversationManager is nil, falling back") _fallbackReportIncomingCall(call: call, uuid: uuid, handle: handle, hasVideo: hasVideo, displayName: displayName) return } let callInfo = callInfos[uuid] let callId = callInfo?.callId ?? "" let remoteHandle = Handle(type: .generic, value: handle, displayName: displayName) let update = Conversation.Update(localMember: nil, members: [remoteHandle], activeRemoteMembers: [remoteHandle]) // 冷启动时 iOS PKPushRegistry 要求在 2 秒内上报来电,否则杀进程。 // Task { @MainActor } 是异步的,调试时主线程 RunLoop 来不及调度就超时了。 // 这里用 DispatchSemaphore 在后台线程同步等待 LCK 上报完成。 let semaphore = DispatchSemaphore(value: 0) var lckError: Error? DispatchQueue.main.async { Task { @MainActor in do { try await manager.reportNewIncomingConversation(uuid: uuid, update: update) Log.info("[ProviderDelegate-LCK] Reported incoming conversation: callId=\(callId), uuid=\(uuid)") if TelecomManager.shared.endCallkit { CoreContext.shared.doOnCoreQueue(synchronous: true) { core in let linphoneCall = core.getCallByCallid(callId: callId) if linphoneCall?.state == .PushIncomingReceived { try? linphoneCall?.terminate() } } } } catch { Log.error("[ProviderDelegate-LCK] Failed to report incoming conversation: \(error)") lckError = error } semaphore.signal() } } let waitResult = semaphore.wait(timeout: .now() + 5) if waitResult == .timedOut { Log.error("[ProviderDelegate-LCK] Timed out waiting for LCK report, falling back") _fallbackReportIncomingCall(call: call, uuid: uuid, handle: handle, hasVideo: hasVideo, displayName: displayName) } else if let error = lckError { Log.error("[ProviderDelegate-LCK] LCK report failed: \(error), declining SIP call") // 来电被拒(勿扰/黑名单等),decline 掉 SIP 侧 CoreContext.shared.doOnCoreQueue(synchronous: true) { _ in try? call?.decline(reason: .Busy) } } }
Replies
3
Boosts
0
Views
809
Activity
4d
NSE Filtering for encrypted incoming calls: what technical details should we provide?
We’re preparing the first iOS release of ANTINTWRK, an encrypted messenger with voice and video calls. Our push gateway sends a regular APNs alert for the encrypted event. On the receiving device, the Notification Service Extension fetches and decrypts the referenced event. In this delivery path, the gateway does not distinguish an encrypted call invitation from a message. When the extension identifies a ringing call, it uses CXProvider.reportNewIncomingVoIPPushPayload to hand it off to CallKit and suppresses the original alert to avoid a duplicate notification. Our Notification (NSE) Filtering request, submitted on October 25, 2026, still shows Submitted. Xcode cannot export the App Store build because the extension’s distribution profile lacks com.apple.developer.usernotifications.filtering. We have contacted Developer Support under Entitlements. We’re following Apple’s Sending End-to-End Encrypted VoIP Calls guidance. For this design, what technical details or test evidence should we provide so the capability review team can evaluate the request? Is there a recommended way to attach that material to the existing request? We can provide the request and support case IDs privately if needed.
Replies
0
Boosts
0
Views
144
Activity
6d
Apple Watch Notification Center timestamp drift on notifications processed by a Notification Service Extension
I'm seeing a timestamp display issue on Apple Watch Notification Center, and I'd like to confirm whether this is a known watchOS behavior or whether there's a setup mistake on our side. Symptom The same APNs notification displays the correct time on iPhone Notification Center and on the initial Apple Watch banner. After the Watch screen turns off and the user later opens Notification Center on Apple Watch, the same notification may show an incorrect relative timestamp such as "3 hours ago" or even "yesterday". The drift is per-notification and persists for that notification until it's dismissed. iPhone NC always shows the correct time. WhatsApp tested side-by-side on the same iPhone/Watch pair does not show this drift. Setup iOS 26.4.2 on iPhone 16 Pro watchOS 26.4 on Apple Watch Series 10 App with paired Apple Watch A UNNotificationServiceExtension that decrypts E2EE message previews and applies Communication Notification enrichment via INSendMessageIntent and content.updating(from:) Production APNs environment, TestFlight builds No beta software Isolation tests already performed Test mutable-content NSE invoked Drift on Watch NC Minimal APNs (alert + sound only) no no no drift NSE skips content.updating(from:), INInteraction.donate/delete (still calls them as no-op via diagnostic build) yes yes — modifies content drift NSE bypasses ALL Intents/Communication Notification APIs (no INPerson, no INSendMessageIntent, no avatar, no updating(from:)); just modifies title/body/sound/category and returns the mutable copy yes yes — modifies content drift Production-like APNs payload (thread-id, target-content-id, category, sound, badge, custom userInfo) but WITHOUT mutable-content no no no drift Eliminated as causes: content.updating(from:), INSendMessageIntent, INInteraction.donate, INInteraction.delete(with:), INPerson/INPersonHandle (not even constructed in test 3), avatar fetching, thread-id, target-content-id, category, sound, badge, custom userInfo, custom createdAt timestamp, stale Siri/Apple Intelligence history (cleared manually on iPhone and Watch). The pattern The only consistent variable distinguishing the no-drift cases from the drift cases is whether mutable-content: 1 is set on the APNs payload (i.e. whether the UNNotificationServiceExtension is invoked). Once invoked, the extension's behavior with respect to Communication Notifications does not seem to affect the outcome — the drift reproduces even when the NSE only modifies title/body/sound and returns. Questions Is there a known watchOS behavior where notifications processed by a UNNotificationServiceExtension use a different timestamp source on Apple Watch Notification Center after the Watch screen has been turned off and reopened, while the initial Watch banner and iPhone Notification Center show the correct delivery time? Are there specific UNMutableNotificationContent properties or APNs payload flags that should be preserved (or avoided) when returning content from an NSE to keep the Watch NC timestamp consistent with the delivery time? For E2EE messaging apps, is there a recommended pattern to decrypt and return content from an NSE that avoids this drift on watchOS? Happy to provide an anonymized snippet of NotificationService.swift and the APNs payload format if useful. Thanks.
Replies
8
Boosts
0
Views
1.8k
Activity
1w
NSE - Notification Filtering Entitlement - No Progress in Months
It's been 2+ months now since I've submitted an entitlement request for the Notification Service Filtering Entitlement (NSE). I have a mobile app that I transferred from a previous developer account due to business reorganization and the previous account had this entitlement. However, after transferring the app, I am unable to push any updates to the app on iOS because the new developer account does not have the same entitlement. Everything outside of the developer account that the app is associated to remains the same - same workflow, same audience, same app use cases, etc.. However, we still have not had any progress on receiving the entitlement even after multiple escalations and follow-ups with the Apple Developer Support team. I am curious to know if any others within the Developer Community have requested this specific entitlement before and what your experience has been with it? Any advice on how I can expedite the approval for the entitlement? Otherwise our app continues to go stale on the iOS app store.
Replies
1
Boosts
1
Views
989
Activity
1w
NSE Filtering Entitlement lost after app transfer, now blocked from shipping updates to a live app (Request ID: 3T2KH34RB3)
Hi all, Our iOS app is an end-to-end encrypted collaboration app with live customers. It was transferred to our new developer team on October 14. Before the transfer, the app had the Notification Service Extension Filtering entitlement. The entitlement did not carry over to the receiving team, and we didn't realize that until after the transfer was complete. Our pushes are end-to-end encrypted, so we can't ship a build with important updates to our customers without it. What we've done so far: Submitted the entitlement request (Request ID: 3T2KH34RB3) Opened an Apple Developer Support case on October 26 (Case #103009182658) asking for the request to be expedited Followed up by email several times and through the support form, with no response so far Our questions: Is there a process for restoring a previously approved entitlement to the receiving team after an app transfer, rather than going through a new review? Can someone confirm our request is in the review queue and share an estimated timeline? Is there anything else we can provide to help move this forward?
Replies
0
Boosts
0
Views
53
Activity
1w
APNs proper behavior when connections are reset without warning
The company I work for sends large amount of traffic to APNs on behalf of our customers, with rates up to 50k/second at peek times. While a vast majority of the messages are successful or return a proper error code that we can parse and honor, roughly 1.5 million times per day our connections are being closed without warning. The networking library we use, https://github.com/hyperium/h2, is exposing these as ErrorKind::ConnectionReset or ErrorKind::BrokenPipe. From our reading of the APNs documentation, it is unclear what the correct response is when this occurs. There is no idempotency key included with our messages, so attempting to resend the message again seems frought with the potential for double sends. However, it some cases it seems clear that at least some of the messages in flight over that connection where never sent out at all. We found this open source project unconditionally retrying messages in this case. https://github.com/rpush/rpush/pull/734 Could someone from the APNs team please lay out the expected behavior a client should have when our connection is unexpected closed in this manner?
Replies
4
Boosts
1
Views
593
Activity
1w
Keeping monitored regions in sync with server changes when background pushes aren’t delivered
Our app logs workers’ arrival and departure at work sites using CLLocationManager region monitoring (up to 20 circular regions, “Always” authorization). Each worker’s list of sites changes on our server (daily schedule, occasional same-day changes). When it changes, we send a background push (apns-push-type: background, apns-priority: 5, aps containing only content-available: 1), and the app fetches the new list and re-registers its regions. On real users’ iPhones (iOS 26.6.2) these pushes often aren’t acted on for hours. It’s typically a newly installed app the user rarely opens, sometimes swiped away, possibly in Low Power Mode. Users won’t open the app or change settings. Region monitoring itself works well for us, including relaunching the app after a swipe-away. We understand background pushes are best-effort, so we’re planning to: fetch the list whenever the app is relaunched by a region event pre-load the next work day’s sites in advance coalesce pushes (max ~2/hour per device) Questions: Is there a recommended way to keep monitored regions in sync with server-side changes for an app the user rarely opens, without user interaction or broader location tracking (we want to avoid significant-location-change for privacy reasons)? If the app is relaunched by a region event, is it fine to do a network fetch and re-register regions in that same background launch? As a fallback when a device hasn’t fetched after a change, would an alert push with mutable-content and a Notification Service Extension that downloads the new list be an acceptable use? On iOS 26, does region monitoring still relaunch an app that was swiped away from the app switcher?
Replies
0
Boosts
0
Views
81
Activity
1w
Notification filtering entitlement for an on-call pager heartbeat — none of the form's use cases fit
We build an internal on-call pager app for our engineers, distributed through TestFlight only. Our server sends a heartbeat push to each device every 4 hours. The Notification Service Extension uses it to re-arm a dead-man's-switch alarm on the device: if heartbeats stop arriving, the alarm goes off and the engineer knows the paging pipeline is down. The heartbeat has to be an alert push with mutable-content, because that is the only push type that reliably launches the extension, including when the user has swiped the app away. Background pushes don't work here: they are throttled and are not delivered to an app the user has force-quit, so the dead-man alarm would fire falsely. The problem is that every heartbeat leaves an entry in Notification Center. It carries nothing actionable, and it teaches on-call engineers to ignore notifications from a pager app. Real alerts are always shown, and the extension still shows a visible notification when a heartbeat detects a problem (missed alerts, failure to re-arm). We already send heartbeats with interruption-level passive and an apns-collapse-id, so it is a single quiet entry, but it is still there. com.apple.developer.usernotifications.filtering would solve this exactly. However, the request form requires picking one of four use cases (end-to-end encrypted messaging, earthquake warnings, education alerts, healthcare alerts), and ours is none of them. An earlier reply on this forum said other use cases are welcome to apply (https://developer.apple.com/forums/thread/676672), but the form no longer offers a way to describe one. Questions: Can an app whose use case is outside the four listed apply for the entitlement? If so, how should we fill in the required use-case field? If not, is there a supported way to have an alert push launch the extension without leaving an entry in Notification Center? For example, is it supported for the extension to remove its own delivered notification with removeDeliveredNotifications(withIdentifiers:) after calling the content handler? Thanks!
Replies
2
Boosts
0
Views
188
Activity
1w
Notifications not enabled on my app
I have set up my app to allow for notifications and had previously tested it and it was working. Now, when I or others go into settings on our phones and go to the app, notifications is not even an option. When I go into settings and go to Notifications, the app doesn't even show up in the list. As mentioned, we had previously been able to receive notifications and the Key is set up to do so. Thanks for your help!
Replies
0
Boosts
0
Views
33
Activity
1w
AlarmKit — stop automatically at the end of a custom sound while the app is suspended
We are building a scheduled-audio app. We need a complete custom recording to start at a scheduled time while the device is locked, play exactly once, and stop automatically without user interaction. The app may be suspended at the scheduled time. Environment: iPhone 11, iOS 26.6.1; Xcode 26.6 with iOS 26.5 SDK; deployment target iOS 26.1. The app was signed for development, installed, and launched without an attached debugger. Alarm authorization was granted. No background audio mode or countdown Live Activity is configured. We bundle a 154.017959-second, mono 44.1 kHz 16-bit PCM CAF in the main bundle. The recording was converted to CAF without trimming. Minimal scheduling code, called after successful authorization (using the generic example filename sample-sound.caf): import ActivityKit import AlarmKit import SwiftUI struct PlaybackMetadata: AlarmMetadata {} @MainActor func schedulePlaybackTest() async throws { let attributes = AlarmAttributes( presentation: AlarmPresentation( alert: .init(title: "Audio playback test") ), metadata: PlaybackMetadata(), tintColor: Color.teal ) let configuration = AlarmManager.AlarmConfiguration.alarm( schedule: .fixed(Date().addingTimeInterval(60)), attributes: attributes, sound: .named("sample-sound.caf") ) _ = try await AlarmManager.shared.schedule(id: UUID(), configuration: configuration) }NSAlarmKitUsageDescription is present in the built Info.plist. Reproduction: schedule, lock the phone before the fire date, then leave it locked and listen through the end. The recording starts automatically and plays completely, but then repeats. This is a single fixed alarm, not a repeating schedule. Questions: Is there a supported public configuration for playing a custom AlarmKit sound once and dismissing/stopping the alarm at end of file? If not, is there an OS-managed maximum alert duration, scheduled stop, or guaranteed callback that can meet this requirement when the app is suspended or terminated? Is unattended play-once-and-stop unsupported with the current public APIs, so that this should be filed as an enhancement request? We understand that postAlert describes a subsequent countdown, and that stop(id:) can be called by executing app code. A foreground timer or a user-triggered stop intent would not meet the requirement. We want an intended public API solution appropriate for App Store distribution.
Replies
0
Boosts
0
Views
31
Activity
2w
APNs Delivery Metrics: What Exactly Triggers “Discarded - Disabled”?
Hello, I'm trying to understand the exact meaning of the APNs delivery status Discarded - Disabled shown in Apple's Push Notification Console. According to the status tooltip: Push notifications which were discarded by APNs, because the push feature was disabled for the application on the target device. None of these were saved to APNs storage. However, I'm unable to reproduce this behavior by disabling notifications through iOS Settings. My test scenario I performed the following test on a physical iOS device: Installed our application. Enabled notifications for the application in iOS Settings. Sent a regular visible push notification (alert) from CloudKit console. Checked the individual APNs Delivery Log. The status was Delivered to Device. Disabled notifications for our application through Settings → Notifications → [Our App] → Allow Notifications. Sent another regular visible push notification using the same device token. Checked the individual APNs Delivery Log again. Unexpected result: Despite notifications being disabled in iOS Settings, APNs reported Delivered to Device, not Discarded - Disabled. I'm checking individual notification delivery records, not aggregated metrics. Questions I'd appreciate clarification on the following: What exactly does Apple mean by "the push feature was disabled for the application on the target device"? Does Discarded - Disabled refer to the notification authorization status (UNAuthorizationStatus.denied) or a different device-side state? If disabling notifications through iOS Settings does not trigger this status, what specific user action or device configuration does? Is there a distinction between disabling notification presentation and disabling remote push delivery at the APNs level? Under what exact circumstances does APNs report Discarded - Disabled instead of Delivered to Device? Additional information Push type: alert Notification type: Regular visible notification Device: iPhone 14 iOS version: 27.2 APNs environment: Sandbox My goal is to understand the exact technical conditions that produce Discarded - Disabled, rather than just the general meaning of the status. Has anyone encountered this behavior or received clarification from Apple about this particular APNs delivery status? Thanks!
Replies
0
Boosts
0
Views
106
Activity
2w
PushKit + CallKit for opt-in monitoring alerts?
Hi, Is it permitted to use PushKit and CallKit for monitoring alerts that users explicitly enable? An API event would trigger an incoming call, displaying the monitoring channel as the caller. Answering would acknowledge the alert and end the call, without establishing a voice connection. Alternatively, the app could read the alert locally using AVSpeechSynthesizer after answering. Are either of these approaches permitted, or is a network-based voice connection required?
Replies
1
Boosts
0
Views
127
Activity
2w
watchOS Standalone App Notification Settings Not Appearing
I'm having an issue on my standalone watchOS app where the settings to adjust notifications does not appear anywhere on the iPhone or the Watch. I have successfully requested notifications access from the user and have successfully displayed a local notification to them. However, if the user ever decides to revoke my notification access (or if they deny originally and want to change), the settings pane for notifications does not appear anywhere. I've looked in the following places: On the watch in Settings > Notifications, however it looks like you can no longer edit per app notification settings directly on the watch (none of the installed apps on my watch appear in here). The only options are settings like "tap to show full notification" and "announce notifications" which affect all notifications (Why not? Especially for apps that don't have a iPhone companion app?). On the iPhone in the Watch app (the app you set up your watch in), in Watch > Notification. My app does not appear anywhere in there. On the iPhone in the iPhone Settings app, in Settings > Notifications. My app does not appear anywhere in there. On the iPhone in the iPhone Settings app, in Settings > Apps. My app does not appear anywhere in there I've tried: Adding capabilities in Signing & Capabilities for Push Notification, Time-Sensitive Notifications and Communication Notifications Building the app for release instead of debug My app also requires location access and has successfully appeared in the settings pane directly on the watch in Settings > Privacy & Security > Location Services, however notification settings do not appear anywhere. I have created a stripped down test app to try and that also does not work. This test code successfully asks the user for permission and (from a button in ContentView), successfully schedules a notification and displays it to the user when they're not in the app. Here's the code for my NotificationManager: import UserNotifications class NotificationManager: NSObject, ObservableObject, UNUserNotificationCenterDelegate { static let shared = NotificationManager() @Published var hasAuthorisation = false private override init() { super.init() UNUserNotificationCenter.current().delegate = self requestAuthorisation() } func requestAuthorisation() { UNUserNotificationCenter.current().requestAuthorization(options: [.alert, .sound]) { authorised, error in DispatchQueue.main.async { if let error = error { print("Error requesting notifications: \(error.localizedDescription)") } self.hasAuthorisation = authorised } } } func scheduleNotification(title: String, body: String, timeInterval: TimeInterval) { let content = UNMutableNotificationContent() content.title = title content.body = body content.sound = .default let trigger = UNTimeIntervalNotificationTrigger(timeInterval: timeInterval, repeats: false) let request = UNNotificationRequest(identifier: UUID().uuidString, content: content, trigger: trigger) UNUserNotificationCenter.current().add(request) { error in if let error = error { print("Error scheduling notification: \(error.localizedDescription)") } else { print("Notification scheduled successfully.") } } } } This issue has persisted across two iPhones (recently upgraded) and the watch was wiped when connecting to the new iPhone. Am I missing some code? Am I missing some flag I need to set in my project somewhere? Please can someone with an Apple Watch try this code in a standalone watchOS app and see if the notifications pane appears anywhere for them? I've contacted Apple DTS, but they're taking a while to respond.
Replies
2
Boosts
1
Views
1k
Activity
2w
Please a reply , I'm loosing my mind.
hi so submitted my app 2 weeks ago , still sitting in "waiting for review" 8 emails later. .... not a single word , no relpy to tell me whats happining. As im sure eveyonr did. , we work our hearts out creating the apps , Apple please understsnd how incredibly fustrating this is, please. i begging you , please advise when i will get any communication . i apriciate you may be busy. just tell me that then please.
Replies
0
Boosts
0
Views
23
Activity
2w
NSE filtering - no reply in >30 days
Hello, I submitted a couple of requests with justification for NSE filtering on an app of mine, but I have not received correspondence on either. The initial ticket is RY24AB5J5T, if anyone who reviews them happens to see this post. Happy to hop on a call, exchange emails, or anything else that may be required to process it toward a conclusion. 🙂
Replies
0
Boosts
0
Views
139
Activity
3w