Does google have new API urls #9
Comments
|
Hi @dennis1804 |
|
Hi, thanks for the reply I'll take a look at it this weekend |
|
Hi @dennis1804 |
|
So from what I researched for #3 there is new routes to implement |
|
@williamdes hello, I see that you are already working on this issue, currently I am using this package for some of my projects I noticed that it's not sending notifications to some users while it does send it to others. I assume that FCM legacy APIs will stop working very soon. So, have you started implementing this new APIs? I also did some research and find this way of migrating the APIs from legacy to V1: I may try to migrate it by myself and if it's working then I may add pull request on your repo. |
Hi @mazimez
Probably, did you see some deadline somewhere ? I welcome contributions on this subject, I did not start coding for this subject. Only some documentation reading :) |
|
@williamdes I didn't see any Deadline (till now) but yes, in Firebase console, getting the "FCM_SERVER_KEY" for new Accounts does require some extra steps, so I think Google will first update the Firebase console according to new APIs, and then they may announce Deadline. |
Thank you so much ! 💪🏻 |
|
Hi Team,
We’re writing to let you know that starting June 20, 2024 the legacy Firebase Cloud Messaging (FCM) APIs will be discontinued.
What do you need to know?
On June 20, 2024, we’re reducing the number of Firebase Cloud Messaging (FCM) legacy register APIs and legacy send APIs that provide similar functionality. This step will allow us to provide you with a more consistent experience and align with Google security standards to improve security, reliability and performance. Because of these API decommissions, some already-deprecated SDKs and features will stop working after June 20, 2024. Please consult the tables below to find which Firebase Cloud Messaging (FCM) APIs and corresponding services/SDKs/features will be discontinued and replaced with new alternatives.
Your Firebase project(s) that use Firebase Cloud Messaging APIs are listed below:
We’re here to help
Thanks,
Todd on behalf of the Firebase team
Hi Team,
We’re writing to let you know that starting June 20, 2024 the legacy Firebase Cloud Messaging (FCM) APIs will be discontinued. On June 20, 2024, we’re reducing the number of Firebase Cloud Messaging (FCM) legacy register APIs and legacy send APIs that provide similar functionality. This step will allow us to provide you with a more consistent experience and align with Google security standards to improve security, reliability and performance. Because of these API decommissions, some already-deprecated SDKs and features will stop working after June 20, 2024. Please consult the tables below to find which Firebase Cloud Messaging (FCM) APIs and corresponding services/SDKs/features will be discontinued and replaced with new alternatives. Discontinued Send API Decommissioned service New alternative Legacy HTTP Protocol Sending messages via the Legacy HTTP API. Send messages via the HTTP v1 API. XMPP Protocol Sending upstream and downstream messages via the XMPP API. Send downstream messages via the HTTP v1 API. Send upstream messages via HTTP/gRPC directly from the App to your server. Batch send API Including multiple send requests in a single HTTP request to FCM known as Batch Send. Send messages via the HTTP v1 API, which has been optimized for fanout performance Discontinued Register API Decommissioned SDK New alternative GCM register API Google Cloud Messaging(GCM) SDKs (deprecated in 2018). Latest FCM Android SDK. Legacy Web register API FCM JS SDK version<7.0.0 (deprecated in 2019) Latest FCM JS SDK. Instance ID Server API for Web No SDK related to this API. Latest FCM JS SDK. Discontinued Feature Decommissioned service New alternative Server keys Authenticating requests with server keys. Authenticate requests with access tokens generated from authorized service accounts Sending messages via FCM’s direct channel to iOS devices while they are running in the foreground. All iOS messages will be sent via APNS channel. What do you need to do? Take the following actions before June 20, 2024, to ensure that you have access to the latest supported features and to reduce the risk of future decommissions affecting your usage: Platform Recommended FCM SDK version Android
iOS
Web (Javascript)
Your Firebase project(s) that use Firebase Cloud Messaging APIs are listed below: |
Years later and I'm here again, I wanted to use this amazing package for my new project but what you just posted worries me, are you planning to add support before |
|
Also it seems to be disabled on new projects: 
|
Thank you for refreshing this topic. I intend to try to find time to fix this as this will also hit the production of my client. Nobody did fund any of my work at @code-lts or seems to love this library. But since I took the personal commitment of maintaining libs in @code-lts action will be taken months before it's too late. If users dislike the solution that will be up to them :) The people that will comment on this topic will act as votes for the future of this forked project. Let's continue pushing notifications ;p
Oh.. |
That sounds great, I always did and do appreciate your work and specially this repo. The thing is that this repo was and still is seriously underrated, and the main reason for that is it's really hard to find if there was a reference in the repo that this was made from it would catch on much sooner and better, and there are lots of other places that this could be introduced but sadly isn't, I personally found it by remembering the name of code-lts but I remember using a tool to find the best fork of the main repo every time I wanted to find this repo, and if you have the same problem with your other repos that's the only reason :) This library is the only usable solution that I could find: Which mentions it's using this library under the hood: The library itself isn't as well written and well documented as your version of course and has a lot of problems such as : But the one it uses under the hood may be helpful for your future implementation :) wish I had more time to help you out with it. |
|
Hi everyone here ! I am thinking about considering removing all the code of this library to only keep the main classes to avoid as much BC breaks. That said this very famous library lacks funding: https://github.com/kreait/firebase-php/releases/tag/7.5.2 If I use it, I will do my best to let the users know they should fund it. The important question reading #22 For now all this is hypothetical, feedback is welcome. Other option: stop maintenance of this library in 06/2024 when google drops the API. Other option: copy some code from kreait/firebase-php and make it compatible at least PHP 7.4 (see #22 )
Thank you for the reference ! |
|
I updated the call for funding to be less "threatening"😅, but the SDK is stable, and I will keep it working, just my motivation to invest large amounts of time is reduced. I appreciate you for mentioning it, thank you! ❤️ That being said, the next major version (8.0) that I will release shortly after the release of PHP 8.3 will only support PHP 8.2 and 8.3, according to the supported versions matrix in the README of the SDK. The current version (7.x) will receive security support as long as PHP 8.1 receives security support, so, until release 9.0 of the SDK. But as I said, the SDK is stable and should work with the 7.x version as long as Firebase doesn't drop other APIs. I'm not saying this to push you to continue using the SDK, but if you decide to copy the relevant code, you would need to adapt/test it yourself. I know you know this already, I just wanted to mention it for the sake of completeness 😅. |
|
Thank you @jeromegamez ! |
Hi all, yesterday I had some issues with Google's endpoint (/fcm/send) when I looked at the docs https://firebase.google.com/docs/cloud-messaging/send-message#rest you can see they changed the urls.
The old endpoint seems to work ( apart from the issue I had yesterday: 502 bad gateway)
The text was updated successfully, but these errors were encountered: