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.
@karunstha Жыл бұрын
Tutorial for these steps please? So we need a script always running just to generate/refresh tokens every time we want send the notification?
@philipalveo Жыл бұрын
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
@mmathems395 Жыл бұрын
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.
@Designguidetv11 ай бұрын
how would I get the token each time in my app? I can't run python to manually get that key each time??
@mmathems39511 ай бұрын
@@Designguidetv You're asking this guy?
@dtube123 Жыл бұрын
100% true that google lack in documentation which is wasting developer time. Thanks for the great video
@youssefkhaled1189 Жыл бұрын
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!
@NativeNotify Жыл бұрын
Yeah, Google's documentation is unintelligible
@MrKesie3810 ай бұрын
Awesome been frustrated for many days, until I saw this video
@leonardoduarte200110 ай бұрын
Thanks pal you're the best! You just made an IT student a very happy one :)
@weselyong8 ай бұрын
Thank you, really helps. And glad to know it's not just me found that FCM's document is just like shake.
@shuaibalghazali34058 ай бұрын
Have you been able to implement it bro, please can you guide me🙏
@hah4075 ай бұрын
@@shuaibalghazali3405 have you too? can u help me please hehahah
@assassinofblack15175 ай бұрын
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
@someshsahu4638 Жыл бұрын
i know and i am also irritating from that type of documentation.... very nice and helpful video thank you so much sir...🙏🏼🙏🏼🙏🏼
@shuaibalghazali34058 ай бұрын
From what you understood can you explain how to get the Oauth token please
@lariniabdellah1820 Жыл бұрын
your an angel i've been searching all over for this thanks a lot
@noway2541 Жыл бұрын
Thankyou Thankyou Thankyou So MUCH. I thought I was stupid to not understand the docs.
@gintoki_sakata__11 ай бұрын
Same here 😭
@cabbiewebsite Жыл бұрын
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
@willasaskara Жыл бұрын
oh man this is so frustrating, finally you solved the google documentation maze
@seaux-ryan Жыл бұрын
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.
@shuaibalghazali34058 ай бұрын
Please can you explain how to implement in code, like generate access token
@shuaibalghazali34058 ай бұрын
Because I can't generate access token with Python inside flutter
@jerryworm11 ай бұрын
Thank you so much. You saved my day. I have been pulling my hair over this 😁
@perfect.stealth Жыл бұрын
From my heart. Thank you. I've literally been angry the last few days because of the absolute garbage documentation from Googles side.
@glrbrasil6 ай бұрын
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!
@joaovictormsantos Жыл бұрын
Thank you so much for sharing with the community, you are helping a lot of people, got a new subscriber.
@NativeNotify Жыл бұрын
Thank you!
@gustavoquinocrispin7441 Жыл бұрын
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
@shanokscr9 ай бұрын
Hola, tengo el mismo error, de casualidad lo pudiste resolver?
@aishwaryasonkar64012 ай бұрын
have you find the solution ??
@LuisEnriqueBravoVillalpando2 ай бұрын
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"
@lucidcrean1510 Жыл бұрын
Hahahahha I LOOOOVE your humor!!!!! Great video!!!!
@necdetgedik7 ай бұрын
thank you man i was drowning in the documents you saved me
@esrefzekiparlak Жыл бұрын
Totally agree with all you say! Great content! Thanks!
@gerardhajduk49789 ай бұрын
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.
@NativeNotify9 ай бұрын
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
@shuaibalghazali34058 ай бұрын
@@NativeNotifyplease can you just help with another video on this
@CarlosAntonio8 Жыл бұрын
@NativeNotify, thank you for making my life easier. I don't know what google engineers were thinking when writing the documentation...
@MrBarbasLuis27 күн бұрын
Ajajajajajajaja its the BEST tutorial. I am really frustrated with this new API key acces ajajajajaja. Tks a lot.
@technicalvoice225 Жыл бұрын
You're a life saver. Thanks man
@davidmendes1994 Жыл бұрын
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.
@NativeNotify Жыл бұрын
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
@davidmendes1994 Жыл бұрын
@@NativeNotify oh rough! The hosted server I'm using doesn't support any of those methods, I can only do http posts
@Artiztiko110 ай бұрын
Hi, im in the same situation, i can only use php and dont know how to get my access token@@davidmendes1994
@jerryworm11 ай бұрын
Thanks
@soundaryapalanimuthu2424 Жыл бұрын
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
@KevinFranco-yd5nt7 ай бұрын
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
@NativeNotify7 ай бұрын
What! That's crazy lol
@WhappPayGatway4 ай бұрын
@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
@mauromiotello6 ай бұрын
Is there a way to send formatted text in body ? like bold, new line, etc etc html-> , ?
@TechsBucket7 ай бұрын
Cloud messaging APi page giving error after opening.
@GaryvandenHeever18 ай бұрын
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.
@shuaibalghazali34058 ай бұрын
Please can you explain better to me, like how do I use python to generate a token in flutter it's not adding up
@NativeNotify7 ай бұрын
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
@millennialdiamond6842 Жыл бұрын
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?
@juniorhakeroriginal Жыл бұрын
Same, have you resolved the problem?
@empiregood92254 ай бұрын
How to user POSTMAN from this API, any video?
@markferdiecatabona75956 ай бұрын
@NativeNotify is there a need to update something on the client app (android app) that receives notification ?
@caraleguis4 ай бұрын
en mi caso no ha hecho falta.
@adelashour32535 ай бұрын
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
@MayurShrivas-nk5el6 ай бұрын
How can we pass a key in a bearer access token?
@justo.roberto4 ай бұрын
Thank you very much!
@angelemiliolopezfernandez37007 ай бұрын
jajajaja Genial amigo ! jajaja que simple lo volviste, gracias
@muhammadomran264310 ай бұрын
That's wrong, the key that shows up in service account page is NOT the Bearer token !!!
@NativeNotify10 ай бұрын
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
@mmathems395 Жыл бұрын
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 Жыл бұрын
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?
@mmathems395 Жыл бұрын
@@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.
@ProfessionalBrokeMemer Жыл бұрын
@@mmathems395 there is another video on this channel that really explains well better search it up from his videos
@viKii3993Ай бұрын
as per you guide access token this could not work
@NativeNotifyАй бұрын
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
@hasansalam7663 Жыл бұрын
2:14 copy and paste in app code?? and where can i find it??
@NativeNotify Жыл бұрын
In this code I used nativenotify.com for the push notification service.
@anonymousmangalorean Жыл бұрын
I get the same feeling with all Google APIs
@pabloestebanespinosagranad582611 ай бұрын
Anyone knows how to do it with spring boot and how to test it?
@iqbrb7 ай бұрын
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.
@jonatan40110 Жыл бұрын
I LOVE YOU MAN !!!!!!
@onasogapelumi38366 ай бұрын
God bless you man
@knooroffical7 ай бұрын
what if i want to send notification to multiple devices what will be the payload
@caraleguis4 ай бұрын
puedes hacer que varios se suscriban a un mismo TOPIC y luego notificar a ese TOPIC y todos lo recibirán.
@34_wahdaadellap.f.9 Жыл бұрын
Can I create notifications to be sent to all devices that have the application without a device key?
@bastianbastias292311 ай бұрын
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?
@forester1 Жыл бұрын
I think this was advertisment for nextchat😂😂😂
@Andris_Briedis3 ай бұрын
This was manual for google manual. As sad as it is.
@Basirafeef Жыл бұрын
hello sir thanks for sharing great knowledge, please make a video about how to use this new fcm api in android? thanks
@Akorv Жыл бұрын
No changes in the android app ? I use React Native fyi... Thanks for great content!!!
@VinayKumar-xr4fc6 ай бұрын
u have skipped secret keys json file....with out that it wont happens
@Dev-PauloEd Жыл бұрын
Wait... isn't the next chat just the same as the chat AI made by OpenAI?
@NativeNotify Жыл бұрын
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
@arturmrozinski75367 ай бұрын
bro you are my hero
@brandonbailey832311 ай бұрын
what about ios?
@Eshoormina11 ай бұрын
Bro im getting 401 error
@OnionKnight5417 ай бұрын
@1:48 "this is usually done with a service like Native Notify" 😂
@YPWorkStuff Жыл бұрын
I am still stuck with this new version and unable to do it in java. It was simpler in the old version T_T
@NativeNotify Жыл бұрын
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
@ИванСинякин-м7б Жыл бұрын
Thanks a lot
@louisocarroll8 ай бұрын
anyone had any success doing this with php?
@fullstack_boy Жыл бұрын
what about to send multiple devices.
@NativeNotify Жыл бұрын
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.
@fullstack_boy Жыл бұрын
@@NativeNotify I got the solution two days before.
@abhinavsinghring Жыл бұрын
@@fullstack_boy what is the solution u got
@fullstack_boy Жыл бұрын
@@abhinavsinghring using subscribe multiple devices and then send batch send on subscribed token devices.
@abhinavsinghring Жыл бұрын
@@fullstack_boy can u share code snippets or any post so i can understand further
@zlackbiro9 ай бұрын
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.
@HEITHEMBEN-d5z6 ай бұрын
THANNKKKKKKKKK YOUUUUU
@logicoflife38319 ай бұрын
This is unique
@Codewithedyn Жыл бұрын
Guy so true😂 months! Those documentations are so vague! Let me watch through😩
@SteveNerry6 ай бұрын
Do a tutorial for Azure
@zackdannar66812 ай бұрын
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.
@abdullahawad38511 ай бұрын
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
@areldy53896 ай бұрын
Hello bro, how you make that? I need change that but i understad, the access token expires for what time?
@OnlyNatural77 Жыл бұрын
OMG. Really it was so frustrating. I wasted two days in figuring out.
@leonardocurbelobetancort430 Жыл бұрын
Gracias, aun así es muy complicado. 🥵🥵
@Sagar-sq6kc7 ай бұрын
This is wrong information, This key is not Authorization Bearer Token Auth 2.0
@NativeNotify7 ай бұрын
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
@andrespizarro75286 ай бұрын
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
@TeamBalck Жыл бұрын
Thanks Bro 😘🤍🤍🤍
@natsudragneel788410 ай бұрын
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.
@rap2trap Жыл бұрын
Resumindo a google cagou o Firebase Push Notification. so bagunçou as coisas.
@HSinhori Жыл бұрын
a documentação me faz procurar videos como esse ;)
@LesCandle11 ай бұрын
nonsense that will Not produce a jwt token. Just designed as click-bait
@shanerigsby9030 Жыл бұрын
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.
@matthewpolak91956 ай бұрын
bro really said ask chatgpt
@NativeNotifyАй бұрын
lol that’s the only way I was able to originally figure this out. The Google documentation was unintelligible
@millennialdiamond6842 Жыл бұрын
Super frustrated
@kingsmanSmBanglaGaming Жыл бұрын
Very simple I see
@logicoflife38319 ай бұрын
hi
@iamsantoshnayak3 ай бұрын
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
@kammelna2 ай бұрын
Yeah. btw did u find any solution for this?
@NativeNotifyАй бұрын
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
@allfullform17607 ай бұрын
This is wrong information. This is not an access token.
@silentobserver9646 күн бұрын
Google documentation sucks, but this guy is trying to sell unnecessary products.
@leolima85852 ай бұрын
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.
@NativeNotifyАй бұрын
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
@SamiRahman-o8f10 ай бұрын
@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.
@NativeNotify10 ай бұрын
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.
@onafrica97837 ай бұрын
Thankyou Thankyou Thankyou So MUCH. I thought I was stupid to not understand the docs.