You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 7, 2019. It is now read-only.
Depending on the notification event and payload, the `onMessageReceived` callback is invoked with up to three arguments.
405
405
406
-
* `message` - *String*. A string representation of the `data.message` value in the notification payload.
407
-
* `data` - *Object*. A JSON representation of the `data` value in the notification payload.
408
-
* `notification` - `RemoteMessage.Notification`. A representation of the `RemoteMessage.Notification` class which can be accessed according to its public methods. This parameter is available in case the callback was called from a message with a `notification` key in the payload.
406
+
*`message` - *String*. A string representation of the `data.message` value in the notification payload.
407
+
*`data` - *Object*. A JSON representation of the `data` value in the notification payload.
408
+
*`notification` - `RemoteMessage.Notification`. A representation of the `RemoteMessage.Notification` class which can be accessed according to its public methods. This parameter is available in case the callback was called from a message with a `notification` key in the payload.
0 commit comments