Include actionIdentifier in initialNotification #4883
Unanswered
TNicholson11
asked this question in
Q&A
Replies: 1 comment 5 replies
-
@Ehesp or @Salakar do you know anything about this? I don't - my initial take @TNicholson11 is that it might simply have never been implement just because it wasn't thought of, without thinking farther than that. But I could be wrong! Hopefully Eliot or Mike will answer |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When sending remote notifications with custom actions as described in a IOSNotificationCategory the actionIdentifier is a member of the UNNotificationResponse however it is not included anywhere in the definition of a FCM RemoteMessage nor is it included in the _initialNotification returned by the getInitialNotification method. Is there any particular motivation for this? Is there some limiting factor that I'm unaware of or have I totally overlooked some other solution for determining which action(s) were used to open a remotely triggered FCM notification?
Note: We are paying users of Notifee, however using data-only messages to populate Notifee notifications on the user-side is notoriously unreliable in background scenarios and, as far as I can tell, does NOT work whatsoever in low-power mode on iOS. However, remote FCM Notifications are delivered very reliably BUT without exposure to the actionIdentifier, custom action responses are not supported using FCM messaging alone.
It would be awesome if the actionIdentifier was included in the initialNotification and, if not, I'd be curious to know if there's another solution I have overlooked or if there is some reason that this feature cannot be supported.
Thanks very much!
Beta Was this translation helpful? Give feedback.
All reactions