Migrate from legacy FCM HTTP API to HTTP v1 API

[ghost]

This project's dependency github.com/appleboy/go-fcm uses legacy FCM HTTP API.
Are there any plans to migrate it to the v1 API as recommended by Firebase documentation? Or maybe
integrate Firebase Admin SDK instead of using raw HTTP API.

Also, how can I pass TitleLocArgs and BodyLocArgs values as array of strings? In the dependency mentioned above
these values are defined as plain strings whereas FCM documentation specifies them as array of strings .
When I make a request with TitleLocArgs I get an error Error Message: unknown error type. However when I make same request connecting directly to FCM server everything works fine.

[giovanni-orciuolo]

+1

[cdivita]

+1 also for me

[IlyaGulya]

Hello!
Today Google announced that FCM Legacy HTTP API will be removed on June 20, 2024.
I think now this ticket should get a bit more attention 🙂
https://firebase.google.com/docs/cloud-messaging/http-server-ref

[appleboy]

@IlyaGulya I will take it.

[pvincendeau]

@IlyaGulya I will take it.

Hello @appleboy.
Do you have any idea of a time schedule for the release of a new version using FCM HTTP v1 API instead of the legacy one please ?
Thanks a lot in advance !

[c0olix]

Hey there, I found your promising notification service yesterday. I would really love to use this, but this issue is keeping me from using it. Any chance to get an estimation, when Firebase Cloud Messaging API (V1) is implemented?

Thanks

[c0olix]

Bump

[sankethkini]

@IlyaGulya I will take it.

@appleboy any estimation on by when this will get implemented?

[appleboy]

Hey, sorry about that. I'm planning to kick off the API transition this month, and hopefully, by next month, there'll be a version ready for everyone to test out.

[obuzyig]

Dear @appleboy,

Thank you for your amazing effort.

I have checked out potential authorization methods on FCM HTTP v1 API Documentation and wondered if it is possible to maintain the multi-tenancy on the new approach.

Regarding the previous API, the "api_key" input helps to send notifications to multiple applications. Selecting different "JSON" files, including project-id values, to authorize could be a valuable capability for somehow maintaining multi-tenancy.

[appleboy]

@obuzyig

Thank you for reaching out and for your kind words regarding our efforts.

I'm delighted to inform you that we are fully committed to supporting multi-tenancy on the FCM HTTP v1 API platform. Your feedback regarding the potential authorization methods and the importance of maintaining multi-tenancy is greatly appreciated.

[sankethkini]

#550 (comment)

@obuzyig I am aware of only one feasible method for authorization i.e, using service-account.json files. Are you aware of any other methods as such?

[obuzyig]

#550 (comment)

@obuzyig I am aware of only one feasible method for authorization i.e, using service-account.json files. Are you aware of any other methods as such?

@sankethkini I think FCM provides the Application Default Credentials option for applications that work on a Google-related platform or infrastructure. I do not have any other generic solutions for covering other applications.

[petenickless]

Hey, sorry about that. I'm planning to kick off the API transition this month, and hopefully, by next month, there'll be a version ready for everyone to test out.

Hey @appleboy - just wondering if it's possible to get an update on progress with this. Do you think the upgrade will be ready to be used in production before the legacy HTTP API is switched off in June?

Thanks in advance 👍

[hilariocoelho]

Hey, sorry about that. I'm planning to kick off the API transition this month, and hopefully, by next month, there'll be a version ready for everyone to test out.

Hello @appleboy . Are there any news regarding this subject?

[appleboy]

@hilariocoelho

I am continuing with the development and expect to have a release ready for testing by everyone on 05/10 Taiwan time. Sorry for the late reply.

[appleboy]

Hi All,

Update on current status:

I'm currently trying to resolve the upgrade issue at appleboy/go-fcm#38. Once the package resolves this, I will proceed with the upgrade here. I apologize for the delay in scheduling, and I will keep everyone posted on the progress here."

[appleboy]

Hi All,

Update on current status:

I already update the dependency package go-fcm. Next, I plan to update the Gorush. Maybe next week I can offer the new testing version.

appleboy/go-fcm#38 (comment)

[pvincendeau]

Hello @appleboy

Do you have any estimation on when a final release of gorush implementing the new FCM integration will be available ? The legacy API will be discontinued in less than 3 weeks and we need to know if we have to adjust our plans and look for an alternative or stick with your great solution.

Thanks in advance

[appleboy]

@pvincendeau I will release the new version this week.

[pvincendeau]

Hi @appleboy
Do you have any news on the final release date ? I was hoping that the version will be available today as you told me ealier that it would be available this week. Our application relies on gorush to send push notification and it is one of our major feature. We really need to update as soon as possible and the deadline is now less than two weeks away.
Thanks in advance

[appleboy]

@petenickless Can you give the two days? I will release the first version on Sunday (06/09 UTC+8:00).

[appleboy]

@petenickless @IlyaGulya @hilariocoelho @cdivita I released the v1.18.0 version. Please help to try it out. https://github.com/appleboy/gorush/releases/tag/v1.18.0

[appleboy]

Please feel free to open a new issue if anyone has any further questions.