Skip to content

Add support for specifying target-content-id #155

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mman opened this issue Jan 21, 2020 · 3 comments
Closed

Add support for specifying target-content-id #155

mman opened this issue Jan 21, 2020 · 3 comments

Comments

@mman
Copy link
Contributor

mman commented Jan 21, 2020

When sending a push notification to the iOS 13 multi window app, a notification payload can specify target-content-id value that is later populated into UNNotificationContent when push notification is received and can later be used to target what app window should be brought forward when the notification is tapped.

WWDC video: https://developer.apple.com/videos/play/wwdc2019/259/
APN reference: https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/generating_a_remote_notification
UNNotificationContent: https://developer.apple.com/documentation/usernotifications/unnotificationcontent/3235764-targetcontentidentifier

Looks like a good and simple starter PR where target-content-id is basically populated through the same way mutable-content is.

@funkenstrahlen
Copy link
Contributor

funkenstrahlen commented Jan 24, 2021

This might require adding support for this property to node-apn before this can be used here.

@parse-github-assistant
Copy link

The label type:feature cannot be used in combination with type:improvement.

@mman
Copy link
Contributor Author

mman commented May 15, 2024

This is obviously available for a very long time, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants