Watch fails to send notification response to iOS for dynamically added actions

Originator:mail.junjie
Number:rdar://45035585 Date Originated:October 5 2018, 3:55 PM
Status: Resolved:
Product:watchOS + SDK Product Version:watchOS 5.1 (16R5568d), iOS 12.1 (16B5068i)
Classification:Serious Bug Reproducible:Always
 
Summary:
New in watchOS 5 is the ability to dynamically add or remove notification actions from the notification interface. While developers can indeed add or remove notification actions from the interface, actions that are added are not sending any response to the iOS app, making this feature unusable in practice.

This feature is described in WWDC 2018, Session 206, What's New in watchOS:
"Well, new in WatchOS 5, you can now adjust the action buttons that are shown at runtimeā€¦ which will give you the flexibility to change the action buttons based on how the user interacts with the elements in the interactive notification interface." (https://developer.apple.com/videos/play/wwdc2018-206/?time=533)

Please watch video, and check out attached sample project for bug reproduction.

Steps to Reproduce:
1. iOS app to schedule a notification 10s later so that Watch can pick up the notification
2. watchOS dynamic interactive notification controller to add actions by changing the notificationActions property
3. Tap on any of the new UNNotificationAction that are added

Expected Results:
iOS app to receive the notification response via the delegate func userNotificationCenter(_ center: UNUserNotificationCenter, didReceive response: UNNotificationResponse, withCompletionHandler completionHandler: @escaping () -> Void)

Actual Results:
iOS app does not receive any response at all.

Version/Build:
iOS 12.1 (16B5068i)
watchOS 5.1 (16R5568d)

Configuration:

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!