iOS Question Firebase Sending tool needs update to support Firebase Cloud Messaging V1

mcqueccu

Well-Known Member
Licensed User
Longtime User
I integrated firebase push in my application, and one thing I noticed is the LEGACY Cloud messaging has been disabled, and it's recommended to use the Firebase Cloud Messaging API V1.
The new FCM API v1 token is shorter than the older web API key (which is now disabled by default)



When using the new FCM token (format AIza............), I get this error

B4X: 
Waiting for debugger to connect...
Program started.
ResponseError. Reason: , Response: <HTML>
<HEAD>
<TITLE>INVALID_KEY_TYPE</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<H1>INVALID_KEY_TYPE</H1>
<H2>Error 401</H2>
</BODY>
</HTML>
[jobname=fcm, success=false, username=
, password=, errormessage=<HTML>
<HEAD>
<TITLE>INVALID_KEY_TYPE</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<H1>INVALID_KEY_TYPE</H1>
<H2>Error 401</H2>
</BODY>
</HTML>
, target=class b4j.example.main
, taskid=1, req=anywheresoftware.b4h.okhttp.OkHttpClientWrapper$OkHttpRequest@3911c2a7, response=anywheresoftware.b4h.okhttp.OkHttpClientWrapper$OkHttpResponse@4ac3c60d
, tag=java.lang.Object@4facf68f, invalidurl=https://invalid-url/, defaultscheme=https
, main=null, httputils2service=null]

But when I went to Cloud Messaging API and enabled the Old Cloud Messaging API which is longer and starts AAAA.................., the messaging works.
 
Solution
Google really make thing more complicated.

Migrate from legacy FCM APIs to HTTP v1 | Firebase Cloud Messaging

firebase.google.com

Endpoint:
Before
POST https://fcm.googleapis.com/fcm/send
After
POST https://fcm.googleapis.com/v1/projects/myproject-b5ae1/messages:send

Authorization:
Before
Authorization: key=AIzaSyZ-1u...0GBYzPu7Udno5aA
After
Authorization: Bearer ya29.ElqKBGN2Ri_Uz...HnS_uNreA

Payload:
Before
JSON: 
{
  "to": "/topics/news",
  "notification": {
    "title": "Breaking News",
    "body": "New news story available."
  },
  "data": {
    "story_id": "story_12345"
  }
}
After
JSON: 
{
  "message": {
    "topic": "news",
    "notification": {
      "title": "Breaking News"...
Sort by date Sort by votes

aeric

Expert
Licensed User
Longtime User
You mean the sending tool attached in the first post?

FirebaseNotifications / Push Messages (server not required)

Updated tutorial: https://www.b4x.com/android/forum/threads/b4x-firebase-push-notifications-2023.148715/ The configuration steps are still relevant. Firebase Notifications service makes it relatively easy to send push messages. Integrating Firebase...
www.b4x.com

As far as I know, it has been working all the while.
 
Upvote 0

mcqueccu

Well-Known Member
Licensed User
Longtime User
Thank you @aeric for the response.

Yes in my submission, the tool works with my old projects using the long web API token (AAAA*************)

But the screenshot I posted above shows they are recommending FCM v1 API which when I use with the sending tool, I get the error I posted, and I think something changed in the FCM v1.

Which of the tokens do you use?
Shorter one
AIza******

Or longer one
AAAA*****
 
Upvote 0

aeric

Expert
Licensed User
Longtime User
Sorry, I have been long time not working with FCM. I just checked one of my old apps. It is indeed using the AAAA... version but I remember I was using the one with Alza...
Let me check again and double confirm.
 
Upvote 0

aeric

Expert
Licensed User
Longtime User
Google really make thing more complicated.

Migrate from legacy FCM APIs to HTTP v1 | Firebase Cloud Messaging

firebase.google.com

Endpoint:
Before
POST https://fcm.googleapis.com/fcm/send
After
POST https://fcm.googleapis.com/v1/projects/myproject-b5ae1/messages:send

Authorization:
Before
Authorization: key=AIzaSyZ-1u...0GBYzPu7Udno5aA
After
Authorization: Bearer ya29.ElqKBGN2Ri_Uz...HnS_uNreA

Payload:
Before
JSON: 
{
  "to": "/topics/news",
  "notification": {
    "title": "Breaking News",
    "body": "New news story available."
  },
  "data": {
    "story_id": "story_12345"
  }
}
After
JSON: 
{
  "message": {
    "topic": "news",
    "notification": {
      "title": "Breaking News",
      "body": "New news story available."
    },
    "data": {
      "story_id": "story_12345"
    }
  }
}

To get the ya29.xxxxxxx, we need to use a valid OAuth 2.0 access token. So the question is how I can get this token?

So I modify the project from here:

[class][B4X] Google OAuth2

GoogleOAuth2 class is compatible with B4A, B4i and B4J (new). It is no longer possible to use WebView to implement Google's OAuth2 authentication. The solution is to open the default browser and set the redirection uri in such a way that the browser will redirect the response back to our app...
www.b4x.com

Here is the tested Sending Tool 2
 

Attachments

  • SendingTool2.zip
    4.9 KB · Views: 664
Last edited:
Upvote 1
Solution

aeric

Expert
Licensed User
Longtime User
Take note:
Replace fire-push-24359 with your project ID. I forgot to remove my project id.
B4X: 
Job.PostString("https://fcm.googleapis.com/v1/projects/fire-push-24359/messages:send", jg.ToString)

I only do for sending FCM to B4i app using topic.
Maybe Erel or anyone can improve my code above for sending FCM to B4A and B4i.
 
Upvote 0
You must log in or register to reply here.

Similar Threads

  • Question
iOS Question Clear firebase notification message
Replies
1
Views
309
Erel
  • Question
Other [B4X] Send Firebase Push Notifications with Node Js (2024)
Replies
3
Views
1K
mcqueccu
  • Question
iOS Question Firebase Notifications
Replies
3
Views
759
Semen Matusovskiy
K
  • Question
iOS Question Configured firebase push notification but no response
Replies
3
Views
666
Erel
  • Question
iOS Question Send SMS programmatically
Replies
3
Views
2K
BillMeyer
Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…