Notifications - Unhandled Category - Notification category "(null)" not found

Originator:jverdi
Number:rdar://19075382 Date Originated:24-Nov-2014 05:38 PM
Status:Open Resolved:
Product:Developer Tools Product Version:Xcode 6.2 beta (6C86e)
Classification: Reproducible:Yes
 
Summary:
I'm attempting to test Notifications for a WatchKit app. I have setup my project as described in the documentation.
 
When running a Notifications scheme for a Watch App, I get the following message in the simulator's watch interface:

Unhandled Category
Notification category "(null)" not found. Define this category or a default category in your storyboard.


Steps to Reproduce:

Short version: Try running the “Notifications - Notifications Watch App” scheme in the attached demo project. (https://www.dropbox.com/s/oo4rdc7sihitdt4/Notifications.zip?dl=0)

Long version:
In my storyboard, I have interfaces for 2 notification types, each with static and dynamic versions. I have given them the Notification Category names of category1 and category2. Then in my PushNotificationPayload.json file, I have specified the payload's category as category1. Running the scheme for WatchKit notifications does not display any UI, and instead claims that the category (null) was not found.


Expected Results:
The Notification UI that corresponds to the category supplied in the JSON file is displayed.


Actual Results:
What is displayed instead is:

Unhandled Category
Notification category "(null)" not found. Define this category or a default category in your storyboard.


Notes:
(Side Note: the documentation mentions the test file as being named "RemoteNotificationPayload.json", while Xcode 6.2 (6C86e) creates one called "PushNotificationPayload.json" when creating a Watch App target from the provided template.)

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!