fcmex icon indicating copy to clipboard operation
fcmex copied to clipboard

Published 20 hours ago • verified publisher icon shufo

Support for HTTP v1 API

Open danielxvu opened this issue 6 years ago • 4 comments

Hi,

This seems to be the most popular Elixir library for interfacing with Firebase Cloud Messaging so I thought I'd open a feature request here first. The current Firebase docs recommend that users eventually migrate over to the HTTP v1 API. Are there any plans to add support? Or would you rather accept a pull request?

Thanks for the work!

danielxvu avatar Nov 06 '19 23:11 danielxvu

@danielxvu Thanks for suggestion!

Are there any plans to add support?

Yes, The HTTP v1 API has some feature benefit like below, so it is planned to be implemented.

  • Better security via access tokens
  • More efficient customization of messages across platforms
  • More extendable and future-proof for new client platform versions

Pull Request would also very welcome!

I think it would be better to support both HTTP API and HTTP v1 API because the docs say

Caution: Any apps that use device group messaging may prefer to not upgrade. HTTP v1 does not support this feature of the FCM legacy API.

shufo avatar Nov 07 '19 02:11 shufo

Hi, the Legacy HTTP API will soon be deprecated:

API Name API Endpoint Impact on users Action Required
Legacy HTTP protocol API Endpoint Requests to the endpoint will start failing after 6/21/2024. Migrate to the HTTP v1 API.

Is there any plans to support the new v1 API before then?

dorian-marchal avatar Dec 06 '23 08:12 dorian-marchal

@dorian-marchal Thanks for notifying me. Yes, I have a plan to support HTTP v1 API. Maybe I will update in next 1 month or 2 month.

shufo avatar Dec 06 '23 09:12 shufo

Hello @shufo will you find some time to support the new version, soon, by any chance? Thanks. :bowing_man:

dorian-marchal avatar Feb 23 '24 15:02 dorian-marchal