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.
No follow ups on this? Please show us atleast this With their garbage documentation and forcing us next year to use this, for native FE devs this is a pain in the ass
Okay, understood, you have answered my question about the need of a key which is identical to the Legacy key - because the key generated under this tutorial is rejected by a prompt for the Legacy key.
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!
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
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
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.
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.
You're right, you have to use the generated key to create a bearer key. The bearer key changes every 5 minutes, I think. You need the key from the video when using their API to generate the bearer key right before sending a notification. Services like NextChat.ai will walk you through it. Basically I was wrong when I said you don't need to run the python code in the video. You DO need to run the code
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 you cannot understand how long I have being waiting for this ,it took me almost a month trying to send push notifications and when I migrated from expo push to fcm finding token was like hell thanks for this and wish you show us a tutorial on sending push notifications with images and explain what the extra data is all about
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.
I'm so sorry. If you're following along using NextChat.ai, you DO have to run the python code to generate the access token. 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. You do have to run the code in the video to get the actual access token, I was wrong in the video when I said you can skip that
You're right. You do have to run the function I thought you could skip. I pinned a comment to the top of this that walks through how to get the bearer token. NextChat.ai will also sho you how if you ask it questions
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
justamente el mismo error me da, lo que entiendo es que debe haber un codigo intermedio que este no puso o no ejecuto en donde se obtiene el "Bearer key" haciendo uso de la key que te arroja firebase esa bearer key es temporal y deberia ejecutarse cada peticion antes de enviar el mensaje, ahora el rpoblema es saber que mugrero de codigo es ese que devuelve el "bearer key"
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.
Ask NextChat.ai that question when you get to that step. Copy and paste the Python code and ask it to turn it into flutter code to generate the temporary token
I pinned a comment saying you actually need to use the JSON file downloaded to generate a temporary bearer token using the Python code I thought you could skip. You DO need to run the Python code to get the bearer token
Yes, it uses the same OpenAI ChatGPT service. So you'll get the same great ChatGPT responses. But NextChat.ai is more secure because it doesn't track your conversation data. And NextChat.ai has more features like conversation folders and search bar, prompt creator and folders and search bar, and global prompt library
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?
@@ProfessionalBrokeMemer Moving on from what I understood here, I went back to the official Firebase documents, and I'm still working on it. A combination of the documentation and the right tutorials will fast track to the direction you need. My suggestion would be to continue researching and to be patient - slowly but surely.
Same question from here, maybe we can use topics but im not sure about it. So, where can i get all the token to send my notifications? Do i have to duplicate the data? I mean have the tokens on firebase and in another store to hit the API?
You can't. You have to send them individually. (I've tried to figure that out in the past.) If you want to send them in groups, you have to use a service like NativeNotify.com or use the Firebase portal to send the messages.
I have worked in google cloud for around 10 years. Most of the time I find what I need in the documentation... this documentation for FCM is absolute garbage. Thank you for the video.
You’re right. I pinned a comment saying you actually need to use the JSON file downloaded to generate a temporary bearer token using the Python code I thought you could skip. You DO need to run the Python code to get the bearer token
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
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.
LOL that service account key is not bearer token but you said it is bearer token, before teaching others first learn bro. Don't spread misinformation. Good day
I pinned a comment saying you actually need to use the JSON file downloaded to generate a temporary bearer token using the Python code I thought you could skip. You DO need to run the Python code to get the bearer token
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.
He made a huge mess when explaining, I still have doubts. The creator of this content is more nervous than a learner to understand which message of so many topics he summarizes in seconds of changing screens. Terrible basic tutorial. Improve your line of reasoning, no one here is a robot to understand a sentence of yours in 4 seconds and always changing every 4 seconds. This is your big flaw.
I pinned a comment saying you actually need to use the JSON file downloaded to generate a temporary bearer token using the Python code I thought you could skip. You DO need to run the Python code to get the bearer token
I'm so sorry. If you're following along using NextChat.ai, you DO have to run the python code to generate the access token. 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 (or whatever code you're using). The token in the video is actually the identifier of the json file that is used to generate the access token. You do have to run the code in the video to get the actual access token, I was wrong in the video when I said you can skip that.
![Как отправить Push уведомление? Firebase [Ru, Android] / Мобильный разработчик](http://i.ytimg.com/vi/ym2EpC9yfb8/mqdefault.jpg)
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.
Tutorial for these steps please? So we need a script always running just to generate/refresh tokens every time we want send the notification?
No follow ups on this? Please show us atleast this
With their garbage documentation and forcing us next year to use this, for native FE devs this is a pain in the ass
Okay, understood, you have answered my question about the need of a key which is identical to the Legacy key - because the key generated under this tutorial is rejected by a prompt for the Legacy key.
how would I get the token each time in my app? I can't run python to manually get that key each time??
@@Designguidetv You're asking this guy?
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!
Yeah, Google's documentation is unintelligible
100% true that google lack in documentation which is wasting developer time. Thanks for the great video
Awesome been frustrated for many days, until I saw this video
Thank you, really helps. And glad to know it's not just me found that FCM's document is just like shake.
Have you been able to implement it bro, please can you guide me🙏
@@shuaibalghazali3405 have you too? can u help me please hehahah
oh man this is so frustrating, finally you solved the google documentation maze
Thanks
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
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
What! That's crazy lol
Thankyou Thankyou Thankyou So MUCH. I thought I was stupid to not understand the docs.
Same here 😭
Thanks pal you're the best! You just made an IT student a very happy one :)
your an angel i've been searching all over for this thanks a lot
From my heart. Thank you. I've literally been angry the last few days because of the absolute garbage documentation from Googles side.
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.
Please can you explain how to implement in code, like generate access token
Because I can't generate access token with Python inside flutter
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.
You're right, you have to use the generated key to create a bearer key. The bearer key changes every 5 minutes, I think. You need the key from the video when using their API to generate the bearer key right before sending a notification.
Services like NextChat.ai will walk you through it. Basically I was wrong when I said you don't need to run the python code in the video. You DO need to run the code
@@NativeNotifyplease can you just help with another video on this
thank you man i was drowning in the documents you saved me
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!
I get the same feeling with all Google APIs
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
i know and i am also irritating from that type of documentation.... very nice and helpful video thank you so much sir...🙏🏼🙏🏼🙏🏼
From what you understood can you explain how to get the Oauth token please
Totally agree with all you say! Great content! Thanks!
Thank you so much. You saved my day. I have been pulling my hair over this 😁
You're a life saver. Thanks man
Thank you so much for sharing with the community, you are helping a lot of people, got a new subscriber.
Thank you!
@NativeNotify, thank you for making my life easier. I don't know what google engineers were thinking when writing the documentation...
@NativeNotify you cannot understand how long I have being waiting for this ,it took me almost a month trying to send push notifications and when I migrated from expo push to fcm finding token was like hell thanks for this and wish you show us a tutorial on sending push notifications with images and explain what the extra data is all about
@1:48 "this is usually done with a service like Native Notify" 😂
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.
I'm so sorry. If you're following along using NextChat.ai, you DO have to run the python code to generate the access token. 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. You do have to run the code in the video to get the actual access token, I was wrong in the video when I said you can skip that
@@NativeNotify oh rough! The hosted server I'm using doesn't support any of those methods, I can only do http posts
Hi, im in the same situation, i can only use php and dont know how to get my access token@@davidmendes1994
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.
That's wrong, the key that shows up in service account page is NOT the Bearer token !!!
You're right. You do have to run the function I thought you could skip. I pinned a comment to the top of this that walks through how to get the bearer token. NextChat.ai will also sho you how if you ask it questions
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
Hola, tengo el mismo error, de casualidad lo pudiste resolver?
have you find the solution ??
justamente el mismo error me da, lo que entiendo es que debe haber un codigo intermedio que este no puso o no ejecuto en donde se obtiene el "Bearer key" haciendo uso de la key que te arroja firebase esa bearer key es temporal y deberia ejecutarse cada peticion antes de enviar el mensaje, ahora el rpoblema es saber que mugrero de codigo es ese que devuelve el "bearer key"
I think this was advertisment for nextchat😂😂😂
This was manual for google manual. As sad as it is.
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
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.
Please can you explain better to me, like how do I use python to generate a token in flutter it's not adding up
Ask NextChat.ai that question when you get to that step. Copy and paste the Python code and ask it to turn it into flutter code to generate the temporary token
Thank you very much!
Ajajajajajajaja its the BEST tutorial. I am really frustrated with this new API key acces ajajajajaja. Tks a lot.
2:14 copy and paste in app code?? and where can i find it??
In this code I used nativenotify.com for the push notification service.
Cloud messaging APi page giving error after opening.
How can we pass a key in a bearer access token?
Is there a way to send formatted text in body ? like bold, new line, etc etc html-> , ?
as per you guide access token this could not work
I pinned a comment saying you actually need to use the JSON file downloaded to generate a temporary bearer token using the Python code I thought you could skip.
You DO need to run the Python code to get the bearer token
How to user POSTMAN from this API, any video?
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?
Same, have you resolved the problem?
Hahahahha I LOOOOVE your humor!!!!! Great video!!!!
No changes in the android app ? I use React Native fyi... Thanks for great content!!!
what if i want to send notification to multiple devices what will be the payload
puedes hacer que varios se suscriban a un mismo TOPIC y luego notificar a ese TOPIC y todos lo recibirán.
Wait... isn't the next chat just the same as the chat AI made by OpenAI?
Yes, it uses the same OpenAI ChatGPT service. So you'll get the same great ChatGPT responses.
But NextChat.ai is more secure because it doesn't track your conversation data. And NextChat.ai has more features like conversation folders and search bar, prompt creator and folders and search bar, and global prompt library
hello sir thanks for sharing great knowledge, please make a video about how to use this new fcm api in android?
thanks
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
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?
i dont think he will tell you that, the whole video he is just doing promotions, did you find a solution to it, i am also stuck there?
@@ProfessionalBrokeMemer Moving on from what I understood here, I went back to the official Firebase documents, and I'm still working on it. A combination of the documentation and the right tutorials will fast track to the direction you need. My suggestion would be to continue researching and to be patient - slowly but surely.
@@mmathems395 there is another video on this channel that really explains well better search it up from his videos
@NativeNotify is there a need to update something on the client app (android app) that receives notification ?
en mi caso no ha hecho falta.
Can I create notifications to be sent to all devices that have the application without a device key?
Same question from here, maybe we can use topics but im not sure about it. So, where can i get all the token to send my notifications? Do i have to duplicate the data? I mean have the tokens on firebase and in another store to hit the API?
jajajaja Genial amigo ! jajaja que simple lo volviste, gracias
Anyone knows how to do it with spring boot and how to test it?
what about to send multiple devices.
You can't. You have to send them individually. (I've tried to figure that out in the past.)
If you want to send them in groups, you have to use a service like NativeNotify.com or use the Firebase portal to send the messages.
@@NativeNotify I got the solution two days before.
@@fullstack_boy what is the solution u got
@@abhinavsinghring using subscribe multiple devices and then send batch send on subscribed token devices.
@@fullstack_boy can u share code snippets or any post so i can understand further
Do a tutorial for Azure
Thanks a lot
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.
God bless you man
what about ios?
u have skipped secret keys json file....with out that it wont happens
I am still stuck with this new version and unable to do it in java. It was simpler in the old version T_T
I would use NextChat.ai to ask how to do it in Java. It's an API request at the end that you send to send the notification
THANNKKKKKKKKK YOUUUUU
Bro im getting 401 error
Gracias, aun así es muy complicado. 🥵🥵
anyone had any success doing this with php?
OMG. Really it was so frustrating. I wasted two days in figuring out.
Guy so true😂 months! Those documentations are so vague! Let me watch through😩
This is unique
I have worked in google cloud for around 10 years. Most of the time I find what I need in the documentation... this documentation for FCM is absolute garbage. Thank you for the video.
I LOVE YOU MAN !!!!!!
This is wrong information, This key is not Authorization Bearer Token Auth 2.0
You’re right. I pinned a comment saying you actually need to use the JSON file downloaded to generate a temporary bearer token using the Python code I thought you could skip.
You DO need to run the Python code to get the bearer token
bro you are my hero
Thanks Bro 😘🤍🤍🤍
a documentação me faz procurar videos como esse ;)
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
Hello bro, how you make that? I need change that but i understad, the access token expires for what time?
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
Resumindo a google cagou o Firebase Push Notification. so bagunçou as coisas.
bro really said ask chatgpt
lol that’s the only way I was able to originally figure this out. The Google documentation was unintelligible
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
Very simple I see
Super frustrated
LOL that service account key is not bearer token but you said it is bearer token, before teaching others first learn bro.
Don't spread misinformation.
Good day
Yeah. btw did u find any solution for this?
I pinned a comment saying you actually need to use the JSON file downloaded to generate a temporary bearer token using the Python code I thought you could skip.
You DO need to run the Python code to get the bearer token
hi
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.
Google documentation sucks, but this guy is trying to sell unnecessary products.
He made a huge mess when explaining, I still have doubts. The creator of this content is more nervous than a learner to understand which message of so many topics he summarizes in seconds of changing screens. Terrible basic tutorial. Improve your line of reasoning, no one here is a robot to understand a sentence of yours in 4 seconds and always changing every 4 seconds. This is your big flaw.
I pinned a comment saying you actually need to use the JSON file downloaded to generate a temporary bearer token using the Python code I thought you could skip.
You DO need to run the Python code to get the bearer token
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.
I'm so sorry. If you're following along using NextChat.ai, you DO have to run the python code to generate the access token. 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 (or whatever code you're using).
The token in the video is actually the identifier of the json file that is used to generate the access token. You do have to run the code in the video to get the actual access token, I was wrong in the video when I said you can skip that.
Thankyou Thankyou Thankyou So MUCH. I thought I was stupid to not understand the docs.
Thanks Bro 😘🤍🤍🤍