node-pushnotifications icon indicating copy to clipboard operation
node-pushnotifications copied to clipboard

locArgs on Android not working anymore with v1.6.2

Open pascaljung opened this issue 4 years ago • 5 comments

Hey,

we just updated from v.1.6.0 to 1.6.2 and found that our notifications on iOS were not working anymore (didn't get the locArgs correctly). We found that according to your latest changes we had to provide a JSON string instead of an Array as parameter. Fixing that resolved the issue on iOS, however, Android suddenly stopped working (no notifications delivered to the device anymore). Honestly, I'm not quite sure why this is the case. According to the documentation of node-gcm and what has been discussed in #150, I can understand the change. However, it's not working for us with the new version. Btw: the non-legacy FCM API requires an usual Array instead of a stringified JSON array (see https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages#AndroidNotification.FIELDS.body_loc_args). Maybe it has something to do with that.

For now we fixed the version to 1.6.0 and that's working fine. @alex-friedl do you have any ideas?

Thanks and best, Pascal

pascaljung avatar Mar 17 '21 11:03 pascaljung

@pascaljung for my understanding: with version 1.6.0 you passed an array to locArgs, which worked fine for both gcm and apn, and after the update to 1.6.2 you changed this to a stringified array, but that broke the gcm/Android integration for you?

alex-friedl avatar Mar 17 '21 21:03 alex-friedl

I also checked the docs of node-gcm and Firebase again and it appears that passing a stringified array should be correct?

Not sure if maybe the update to node-gcm 1.0.4 broke things somehow? But judging from their commit history, it shouldn't have. But just to make sure, could you test version 1.6.1, where we still use node-gcm 1.0.3 ?

alex-friedl avatar Mar 17 '21 21:03 alex-friedl

@pascaljung Any update on this? Do you still have the same issue with 1.6.1?

alex-friedl avatar Apr 03 '21 12:04 alex-friedl

Hi @alex-friedl, sorry didn't get to it yet :(. I'll give you an update once I've tried it

pascaljung avatar Apr 08 '21 09:04 pascaljung

@pascaljung Any update? :)

alex-friedl avatar Aug 11 '21 12:08 alex-friedl