This repository was archived by the owner on Sep 4, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 4, 2020. It is now read-only.
Background notification OK, but event "notification" never called #387
Description
Hi everyone,
I installed the plugins and configure android notifications, but, when i send a notification from my server (node-gcm), the notification is shown in the navbar like the application is in the background. If i click in this notification, nothing happened. The most important is if i add a console.log instruction in the "notification" event, nothins is print in the console. So, i think my notification message is never catch by the plugin. Any idea ?
Server message :
var message = new gcm.Message({
collapseKey: "applice",
delayWhileIdle: true,
timeToLive: 3,
notification: {
title: "Hello, World",
icon: "icon",
message: "This is a notification that will be displayed ASAP."
}
});Client side :
self.push = PushNotification.init({
android: {
senderID: "blablablabla"
}
});
self.push.on('registration', function(data) {
console.log('REGISTRATION : ' + JSON.stringify(data));
if (data && data.registrationId && data.registrationId.length >
0) {
// Call token server update
}
});
self.push.on('notification', function(data) {
console.log('MESSAGE : ' + JSON.stringify(data));
// Call client user refresh
});
Activity
macdonst commentedon Nov 30, 2015
@cmillauriaux trying sending this instead and let me know what you find. I recently discovered that Google will just eat messages sent using the "notification" property and not pass them on to the push handler.
cmillauriaux commentedon Nov 30, 2015
@macdonst you're my hero ! Thanks a lot !
I searched desperatly on the plugin side, but it was on the server side. You saved my day !
macdonst commentedon Nov 30, 2015
@cmillauriaux sorry about that, I need to document it better cc: @fredgalvao
fredgalvao commentedon Nov 30, 2015
@macdonst Funny thing, neither of these are technically wrong.
Check node-gcm's usage doc and the official docs on gcm, and you'll see that
dataandnotificationare both declared.data: is supposed to hold extra info, that is passed to the intent on android or to theAppDelegate application:didReceiveRemoteNotification:event on iOS.message,titleoriconare not supposed to live on this object.notification: has its own schemeNow, if what you said is that for some reason we cannot trust in the
notificationobject, I think this should be reported as a bug to google or we're missing something about the handler stuff.fredgalvao commentedon Nov 30, 2015
Oh, I guess I understand now. There is a distinction between
data payloadandnotifications payloadon the docs. Source.Notification payload
Data payload
So, I'm assuming that we want to handle everything by ourselves, which leaves us requiring the
data payloadin every situation.I'll update the docs with a topic on this soon.
macdonst commentedon Nov 30, 2015
@fredgalvao Yup, I found that out while writing a service to send messages using node-gcm. It really tripped me up for awhile. Yes, we will need to be more opinionated and have people use the
dataproperty in their payload instead ofnotification.fredgalvao commentedon Dec 8, 2015
@macdonst , does your comment here has anything to do with this? From what I understood, we cannot simply tell users to ignore the
notificationobject. Or was that comment only for iOS (which makes me think that we need to have pure data objects in android only)?macdonst commentedon Dec 8, 2015
@fredgalvao Yeah, there is an issue with data/notification in that Android and iOS don't treat them the same. I opened #401 to do some testing in the 1.5.x branch. They really should work the same.
MichaelJCole commentedon Mar 19, 2016
FYI: https://github.com/ToothlessGear/node-gcm#gcm-client-compatibility lists this as an open bug (Jan 2016).
Is it still open?
macdonst commentedon Mar 20, 2016
@MichaelJCole send everything in the
datapart of the payload, not thenotifcationpart.sam2x commentedon Feb 16, 2017
Hey, anyone experiencing my case ?
Tried a combinaison of all of them, no luck too.
lock commentedon Jun 4, 2018
This thread has been automatically locked.