Skip to content

Upgrade legacy FCM HTTP API to v1 #150

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.

Sign up for GitHub

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

Jump to bottom
Closed
yagotome opened this issue Oct 31, 2019 · 2 comments
Closed

Upgrade legacy FCM HTTP API to v1 #150

yagotome opened this issue Oct 31, 2019 · 2 comments
Labels
type:feature

Comments

@yagotome
Copy link

yagotome commented Oct 31, 2019 •
edited
Loading

Hello!

I would like to send some properties in Push Notification payload so that I can use them for analytics in Firebase.

However, this adapter still uses legacy FCM API which does not support those properties (such as name, fcm_options.analytics_label etc).

I wonder if you are thinking of migrating to FCM HTTP v1 API soon.
@dplewis
Copy link
Member

dplewis commented Oct 31, 2019

@yagotome There is a PR opened for FCM v1. #116

It's been opened for a while now. Feel free to review, test, and add changes.

@mtrezza
Copy link
Member

mtrezza commented Mar 2, 2024

Closing via #219

@mtrezza mtrezza closed this as completed Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type:feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mtrezza @dplewis @yagotome