-
Notifications
You must be signed in to change notification settings - Fork 373
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
Not clear how to set channel for messaging #168
Comments
Hey there! I couldn't figure out what this issue is about, so I've labeled it for a human to triage. Hang tight. |
Hmmm this issue does not seem to follow the issue template. Make sure you provide all the required information. |
Since it allows arbitrary keys, I would expect that if you just add |
Can something be added to the docs? It's strange the web console has a field for this and nothing is mentioned in the docs for how to do it programmatically. |
@hiranya911 this package no longer allows arbitrary keys in the notification object, how should the android notification channel be set when sending messages? |
You can still use the legacy APIs for this. The new REST API doesn't support it as far as I can tell: https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages#AndroidConfig SDK's |
hey guys, bringing this old thread back to life. it took me a few days to find out how to use firebase admin sdk with node.js and assign a channel ID to a notification. thanks for the post above I just added "android_channel_id" to my notification payload object, see below. It works, but is it the correct way?
followed by something like: |
That looks correct for the legacy API. Channel ID is also supported by the new (v1) API now: https://firebase.google.com/docs/reference/admin/node/admin.messaging.AndroidNotification#optional-channelid |
There's value mentions of android_channel_id in some stackoverflow posts, but nothing in the docs or in this repo. How do you set the channel? The console has a field for it even though the API makes no mention of it.
The text was updated successfully, but these errors were encountered: