Firebase Cloud Messaging API (v1) Tutorial 

I'm so sorry. You DO have to run the python code found in step 3 "Generate the access token" to generate the access token. In the video I said you can skip that part, but I was wrong. The access token has a limited lifespan, so you'll need to run the code each time you want to send a notification to get a new access token. If you use something different like Node.js, you can ask NextChat.ai to change the code into Node.js code. The token in the video is actually the identifier of the json file that is used to generate the access token, NOT the access token itself. You have to use the json file that is downloaded when you create the key in the code found in the NextChat conversation at step 3 "Generate the access token" to get the actual access token. If you're having any issues, just copy and paste any errors into the NextChat.ai conversation and NextChat.ai can help you get to the correct solution. For example, when I tested out the code in this video, I said to NextChat.ai: "i got this error after sending the post request: { "error": { "code": 401, "message": "Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See developers.google.com/identity/sign-in/web/devconsole-project.", "status": "UNAUTHENTICATED" } } I did not run the python code to generate the key. I used the key that was in my Google account" NextChat.ai then told me how to fix the issue I was having.

omg, I am just new to the android world and I thought that I was stupid not to understand the documentations or the google way to get things done. Thank you so much for your help!

your an angel i've been searching all over for this thanks a lot

Awesome been frustrated for many days, until I saw this video

Really thanks sir , i am stuck in this for whole day, but when i watch your video, i understand the whole concept. thanks again sir

Thanks pal you're the best! You just made an IT student a very happy one :)

Thank you so much for sharing with the community, you are helping a lot of people, got a new subscriber.

Thank you for showing where to find the important settings in Google Cloud such as the Firebase Cloud Messaging API and the Service Accounts + Access Key, could not have done it without this video

Thank you so much. You saved my day. I have been pulling my hair over this 😁

Thank you, really helps. And glad to know it's not just me found that FCM's document is just like shake.

Been in GCP and Firebase for 4 years now. It did take a long time to understand service accounts and how they work (I was also new to most cloud dev ops at the time as well). But I actually really appreciate it now. It’s very secure and once you understand every service has an api and that you should make service accounts to secure your apps, it became really intuitive for me.

Totally agree with all you say! Great content! Thanks!

Hi Where to paste the access token key inside outsystems Previously we use server token instead of that shall I use the key inside outsystems

You're a life saver. Thanks man

oh man this is so frustrating, finally you solved the google documentation maze

i know and i am also irritating from that type of documentation.... very nice and helpful video thank you so much sir...🙏🏼🙏🏼🙏🏼

thank you man i was drowning in the documents you saved me

100% true that google lack in documentation which is wasting developer time. Thanks for the great video

I think it is no coincidence that after asking Gemini about how to migrate from legacy FCM APIs to HTTP v1 in his response he recommended this video to me

@NativeNotify is there a need to update something on the client app (android app) that receives notification ?

Hahahahha I LOOOOVE your humor!!!!! Great video!!!!

Is there a way to send formatted text in body ? like bold, new line, etc etc html-> , ?

Postman gives a 401 error when I use the new key as the bearer token; do I need Native Notify to make this whole push notification process to work?

From my heart. Thank you. I've literally been angry the last few days because of the absolute garbage documentation from Googles side.

what if i want to send notification to multiple devices what will be the payload

I think this was advertisment for nextchat😂😂😂

I was trying to make FCM work from Cloud Functions in a Flutter project, no way in hell I would have found out all of these tiny hidden details. Thanks!

@NativeNotify, thank you for making my life easier. I don't know what google engineers were thinking when writing the documentation...

No changes in the android app ? I use React Native fyi... Thanks for great content!!!

I get the same feeling with all Google APIs

Thankyou Thankyou Thankyou So MUCH. I thought I was stupid to not understand the docs.

I LOVE YOU MAN !!!!!!

I like your sarkazm, but at the end two surprising points. 1. The generated key is not Bearer token. 2. BTW, this (not bearer) key can be generated from 4th tab called Service accounts located on the Firebase Project Setting page.

How can we pass a key in a bearer access token?

Anyone knows how to do it with spring boot and how to test it?

The problem I have found is that a prompt is expecting the FCM server key to consist of more characters, so it rejects the key generated under your directions. Would there be a way of generating a key which is identical to the Legacy key please?

No sirve ese bearer token, el key que supuestamente es el token no es: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential

Thanks a lot

Can I create notifications to be sent to all devices that have the application without a device key?

Cloud messaging APi page giving error after opening.

THANNKKKKKKKKK YOUUUUU

God bless you man

hello sir thanks for sharing great knowledge, please make a video about how to use this new fcm api in android? thanks

jajajaja Genial amigo ! jajaja que simple lo volviste, gracias

Wait... isn't the next chat just the same as the chat AI made by OpenAI?

Update: I followed these steps but I received : Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential.

Thank you. Man that was an insane journey ... the mighty google and all. I was begining to think I was really dumb. I was going to abort and use another method. Yeah as you say that python to get the token is the key in fact. Have a blessed day further.

what about ios?

@1:48 "this is usually done with a service like Native Notify" 😂

Guy so true😂 months! Those documentations are so vague! Let me watch through😩

Bro im getting 401 error

2:14 copy and paste in app code?? and where can i find it??

bro you are my hero

I am still stuck with this new version and unable to do it in java. It was simpler in the old version T_T

a documentação me faz procurar videos como esse ;)

This is unique

anyone had any success doing this with php?

Do a tutorial for Azure

Gracias, aun así es muy complicado. 🥵🥵

Google give you tons of constructions and dosnt give any thing in summary or easy way ,why their is a google consol if their is a firebase

Thanks Bro 😘🤍🤍🤍

That's wrong, the key that shows up in service account page is NOT the Bearer token !!!

OMG. Really it was so frustrating. I wasted two days in figuring out.

u have skipped secret keys json file....with out that it wont happens

Make me feel like i am gonna cry, but you give us few tips. They changing things too much, you cant follow even after two weeks.

what about to send multiple devices.

You should get access token first if You could make another tutorial with the correct info I got the solution after a while if you have any quesion just ask me

327 / 5.000 The first time I heard that someone thinks like me... Google has the worst documentation I have ever seen... and it is a multi-million dollar company... this also happens in the google play console... they reject your applications and it never properly explains why what... they just say read the documentation to know what's wrong... it could be all or nothing

Thank you, but I have a simple note. You, too, like Google, make things extremely difficult. This is your video. You can make it only 30 seconds.

Thanks

bro really said ask chatgpt

Resumindo a google cagou o Firebase Push Notification. so bagunçou as coisas.

Very simple I see

hi

This is wrong information, This key is not Authorization Bearer Token Auth 2.0

Super frustrated

Wtf it was really this easy ? Everything is already setup by default all I have to do it create that damn key and everything will works. I have to say google documentation is far to detailed to give us the obvious solution.

nonsense that will Not produce a jwt token. Just designed as click-bait

Their documentation is trash. When looking at examples for a JavaScript web app, they will show some syntax, then on the next page or even the same page show other syntax that is totally invalid. I don't know who their target audience is. I don't even know if a human being puts their documentation together or if it's an amalgam of a big, ugly process. Clearly, they could save us all a lot of time and just have a single human being assigned to document the basics from top to bottom.

This is wrong information. This is not an access token.

@Native Notify i have followed your direction getting the access token but still gettin 401, so i can say that you have waste my time.

Thankyou Thankyou Thankyou So MUCH. I thought I was stupid to not understand the docs.

Thanks Bro 😘🤍🤍🤍