Skip to content
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

Android Beams FCM Token issue #43

Open
scorpionate opened this issue Aug 1, 2023 · 4 comments
Open

Android Beams FCM Token issue #43

scorpionate opened this issue Aug 1, 2023 · 4 comments

Comments

@scorpionate
Copy link

scorpionate commented Aug 1, 2023

I am trying to implement Beams (Android/Flutter).

  1. According to Docs: https://pusher.com/docs/beams/getting-started/android/configure-fcm/
[∞](https://pusher.com/docs/beams/getting-started/android/configure-fcm/#get-your-fcm-server-key) Get your FCM Server Key
Go to your Firebase project‘s settings page, and then go to the Cloud Messaging tab.

You will need to enable the Legacy Cloud Messaging API, not the Firebase Cloud Messaging API.
  1. According to Firebase Console:
Cloud Messaging API (Legacy)Disabled
If you are an existing user of the legacy HTTP or XMPP APIs (deprecated on 6/20/2023), you must migrate to the latest Firebase Cloud Messaging API (HTTP v1) by 6/20/2024. [Learn more](https://firebase.google.com/docs/cloud-messaging/migrate-v1?hl=en&authuser=0)
  1. I can't enable legacy API since Firebase console does not allow it. Beams requires FCM legacy token.

What now?


PS. I enabled from Google Cloud Project Console: https://console.cloud.google.com/apis/library/googlecloudmessaging.googleapis.com

But it's temporary and needs maintenance:

If you are an existing user of the legacy HTTP or XMPP APIs (deprecated on 6/20/2023), you must migrate to the latest Firebase Cloud Messaging API (HTTP v1) by 6/20/2024.

@benw-pusher
Copy link

Hi, we are looking into the requirements for migrating to the new api and will update here once we have completed this.

@Arthurius
Copy link

Hi, we are looking into the requirements for migrating to the new api and will update here once we have completed this.

Any news on this?

@benw-pusher
Copy link

Work is still ongoing at this stage

@ayyoub-coder
Copy link

Kindly, is there any update on this? It has taken a long time, and I'm eager to know if there has been any progress.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants