Using this link GCM/FCM notifications to FCM v1. I am trying to migrate from GCM/FCM notifications to FCM v1. From the guide, I - Configured the Firebase Service Account Credentials in Azure Notification Hub. Updated backend SDK C# code use FCM v1 platform during installation & registration of push notification. Verified that the device is actually registered in notification hub (by getting registrations from notification hub). Checked that Installation is now having the new Platform : FcmV1 instead of Gcm Verified that notification is delivered to app when sent from firebase console. The problem is: I am able to call SendFcmNativeNotificationAsync() and send a notification to the registered device. This is my template according to the migration documentation. "{ "message" : { "notification" : { "body" : "$(message)", "title" : "Test" }}}" and my call to templated notification is $NotificationOutcome = $client.SendTemplateNotificationAsync( $templateParameterDictionary, '$InstallationId:{61D21000-XXXX-}').Result But I am not able to call SendTemplateNotificationAsync() and send a notification to the registered device. When sending notification from "Test Send" in Azure Portal, it does not get delivered. When sending template notification from code (C# - Microsoft.Azure.NotificationHubs nuget), it shows same error.

To post an update: Our engineering team have completed the bug fix and will begin rolling this update today. It will be deployed to all the regions in a phased manner. However, we don't have a concrete ETA to provide for the deployment of the update across all regions. We value your patience and cooperation throughout this process. I completely understand the inconvenience this has caused, and I extend our sincere apologies for the trouble it has brought about.

Issue is solved for us, able to use below implementation without any change from client side. Only change from Server side is installation of devices using the platform FCMv1 and change in the body for the message template. Below is the modified request from server for installation. Highlighted in bold are the changes. { "platform": " FcmV1 ", "pushChannel": "$pushChannel", "installationId": "$installationId", "pushChannelExpired": false, "expirationTime": "9999-12-31T23:59:59.9999999Z", "tags": [ "$installationId" ], "templates": { "MessageTemplate": { "body": " {\"message\":{\"notification\":{\"title\":\"$(title)\",\"body\":\"$(body)\"}}} ", "tags": [ "MessageTemplate" ] } } } @Smitha Kalluparambil Thank you so much!!

PushNotifications: Upgrade to FCMv1 is not delivering Templated Notifications from Azure

Smitha Kalluparambil 80

Using this link GCM/FCM notifications to FCM v1. I am trying to migrate from GCM/FCM notifications to FCM v1.

From the guide, I -

Configured the Firebase Service Account Credentials in Azure Notification Hub.
Updated backend SDK C# code use FCM v1 platform during installation & registration of push notification.
Verified that the device is actually registered in notification hub (by getting registrations from notification hub).
Checked that Installation is now having the new Platform : FcmV1 instead of Gcm
Verified that notification is delivered to app when sent from firebase console.

The problem is:

I am able to call SendFcmNativeNotificationAsync() and send a notification to the registered device.
1. This is my template according to the migration documentation. "{ "message" : { "notification" : { "body" : "$(message)", "title" : "Test" }}}" and my call to templated notification is $NotificationOutcome = $client.SendTemplateNotificationAsync( $templateParameterDictionary, '$InstallationId:{61D21000-XXXX-}').Result
But I am not able to call SendTemplateNotificationAsync() and send a notification to the registered device.
When sending notification from "Test Send" in Azure Portal, it does not get delivered.
When sending template notification from code (C# - Microsoft.Azure.NotificationHubs nuget), it shows same error.

Andreas Leitel 40

We do have the same problem.

After updating to FCM v1 (at Server Plane), we are no longer able to send templated notifications using SendTemplateNotificationAsync.
As also described by @Smitha Kalluparambil we are still able to send notifications by using SendFcmV1NativeNotificationAsync(...) method (he mentioned: SendFcmNativeNotificationAsync)
The template structure has been updated to wrap the notification inside a "message".
Firebase Cloud Messaging API (V1) is enabled
FCM V1 Credentials are correctly set on NotificationHub (during migration it should support FCM & FCM V1). "Azure Test" notifications can be sent to device.
We are using the installation method:

Dictionary<string, InstallationTemplate> templates = new Dictionary<string, InstallationTemplate>();
Microsoft.Azure.NotificationHubs.Installation installation = new Microsoft.Azure.NotificationHubs.Installation()
{
  InstallationId = deviceRegistration.InstallationId,
  PushChannel = deviceRegistration.PushChannel,
  Platform = NotificationPlatform.FcmV1,
  Templates = templates,
  Tags = new List<string>()
          {
              $"env:dev",
              $"principal:C4E4CEB3-0E0D-446A-B5CF-73B2957745C0",
              $"version:V4"
          }
}; 
// add various templates
templates.Add("t-incident", new InstallationTemplate()
{
  Body = JsonConvert.SerializeObject(
        new
        {
          message = new
          {
            notification = new
            {
              title = "$(Title)",
              body = "$(Summary)",              
            },
            data = new
            {
              message = new
              {
                title = "$(Title)",
                summary = "$(Summary)",
                message = "$(Message)"
              }
            },
            content_available = true
          }                
        }
    )
});
// more templates
// ...
// add installation:
await Hub.CreateOrUpdateInstallationAsync(installation);

where the deviceRegistration object is provided by the client
where the templates dictionary is populated with multiple templates, each with keys such as "t-incident" or "t-status".
where the "Tags" property serves as the "installation-key" "by env, principal and an internal Version"

We then send the templated notification by providing the template properties and the tagExpression such as:

var tagExpression = "t-incident && env:dev && principal:C4E4CEB3-0E0D-446A-B5CF-73B2957745C0 && version:V4"
NotificationOutcome outCome = await Hub.SendTemplateNotificationAsync(parameters, tagExpression);

This did work with Microsoft.Azure.NotificationHubs v3.3.0 (FCM legacy)

Since we upgraded to FCM V1 (Microsoft.Azure.NotificationHubs v4.2.0), the above procedure does no longer work.

Any advice?

ajkuma 23,641 Reputation points Microsoft Employee

2024-04-23T09:10:42.5066667+00:00

@Smitha Kalluparambil , Andreas,

Based on my understanding, you are experiencing the issue that we’d addressed here, please check and let us know.

The error "The notification could not be delivered due to an unknown error" occurs.

The problem was resolved by enabling Firebase Messaging API on Google console.
Andreas Leitel 40 Reputation points

2024-04-23T13:47:16.8633333+00:00

@ajkuma

No. this is not the same problem (at least not for us).

We did enable Firebase Cloud Messaging API (V1) on Google Firebase console:

SendFcmV1NativeNotificationAsync works
SendTemplateNotificationAsync does NOT work

We could of course use SendFcmV1NativeNotificationAsync. But that prevents us from working with Installation templates
Smitha Kalluparambil 80 Reputation points

2024-04-24T13:02:13.7166667+00:00

@ajkuma Firebase Cloud Messaging is enabled on our end. This does not fix our issue.

As @Andreas Leitel said it is not the problem

The problem is

SendFcmV1NativeNotificationAsync works SendTemplateNotificationAsync does NOT work
ajkuma 23,641 Reputation points Microsoft Employee

2024-04-24T15:04:35.83+00:00

Andreas, Smitha , Thanks for confirmation and additional info.

Smitha Kalluparambil, While I'm discussing on this internally, will connect with you privately to get additional Info about your resources for a closer investigation.
Andreas Leitel 40 Reputation points

2024-04-24T17:09:03.4266667+00:00

@ajkuma
If required, we could support you as well via private messages. Let me know.
ajkuma 23,641 Reputation points Microsoft Employee

2024-04-25T10:26:13.5966667+00:00

Andreas, thank you for your help with this. On Q&A, we can only initiate a private message with question author/OP. I'll follow-up with you soon.
Luca Lusetti 5 Reputation points

2024-04-26T06:59:42.6566667+00:00

We faced the same proble, sending tests from the Azure Console are delivered but SendTemplateNotificationAsync does not reach the device. Is there any solution ?
ajkuma 23,641 Reputation points Microsoft Employee

2024-05-01T09:27:23.3966667+00:00

Our product engineering team is investigating this issue, as soon as I have more updates, I'll share it here. Thanks for your patience.
Dick Nagtegaal - de Vries 15 Reputation points

2024-05-08T15:37:37.5233333+00:00

The solution to this issue seems to state that template send for FCMv1 does not work with enableTestSend.

For me that seems to be true!

We use the REST API and were sending with test in the query string. When sending a templated message nothing happens (the response indicates 0 succes and 0 failed). But when sending without test the device receives the push notification!

We also couldn't successfully send a template test message from Azure Notification Hub interface (also 0 succes, 0 failed). I think that the Notification Hub always uses a test send.

I wonder if @Luca Lusetti and @Smitha Kalluparambil and @Andreas Leitel can confirm this in their situation.

The problem is though that you must be sure that your template is correct. Without a correct FCMv1 template, the device receives nothing.
ajkuma 23,641 Reputation points Microsoft Employee

2024-05-13T12:15:29.7866667+00:00

Dick Nagtegaal - de Vries, Thanks for the follow-up and update.

Much appreciate you sharing the solution that worked for you with the community.
Serg Tomcat 10 Reputation points

2024-05-13T12:46:09.7166667+00:00

Can confirm @Dick Nagtegaal - de Vries comment, disabling EnableTestSend make templated notifications work with FCMv1.
Andreas Leitel 40 Reputation points

2024-05-13T19:40:21.3+00:00
@Dick Nagtegaal

unfortunately we can not confirm that setting enableTestSend: false fixes our problem. The main difference now seems to be that we are not using the "REST API", but "Microsoft.Azure.NotificationHubs.NotificationHubClient" for sending templated notifications.

@ajkuma Since the documentation related to sending templated notification is not really up to date.. could you provide us (and all others facing the same problem) with a sample that:

Uses the "Hub.CreateOrUpdateInstallationAsync" method

Installs more than one template

Uses a "tag" expression to select one of these templates

... and works?

That would be helpful.
Dick Nagtegaal - de Vries 15 Reputation points

2024-05-14T05:25:02.86+00:00

@ajkuma my "solution" is just a work around in my eyes. I assume Microsoft will fix this problem asap so people can try sending templated messages using the Notification Hub interface again.

Can you please provide feedback on "Our product engineering team is investigating this issue"? You posted that 2 weeks ago. With my "solution" they should have a better understanding of when the issue arises.

Is the engineering team able to reproduce the problem?
ajkuma 23,641 Reputation points Microsoft Employee

2024-05-14T18:42:14.6066667+00:00

Our engineering team have completed the bug fix and will begin rolling this update today. Sorry for the trouble with this issue. I have relayed the feedback to our product engineering team.
tomo-kato 5 Reputation points

2024-05-23T01:30:33.2666667+00:00

------------
Dick Nagtegaal - de Vries 15 Reputation points

2024-05-27T06:43:18.0933333+00:00

@Andreas Leitel Using the REST API I was able to send to a tag expression of "templatename&&tag" and receive a push notification based on the specified template. But again, only when not using Test send. I can't imagine that this wouldn't work via the SDK.
Andreas Leitel 40 Reputation points

2024-05-27T07:50:57.6433333+00:00

@Dick Nagtegaal - de Vries : We are now able to send templated notifications with expressions of templatename&&tag. As I mentioned in a comment to the accepted answer, we had the additional problem of sending nested "data" structures. Before FCMv1 (or SDK 4.2.0 respectively), any nested "data/child" elements were "stringyfied". With the new API, this prevents the submission of notifications to the device. We therefore "flattened" thoses nested structures.
Brad Burrick 0 Reputation points

2024-06-06T13:46:01.34+00:00

We are experiencing this issue SendTemplateNotificationAsync when it comes to FCM v1. Has this fix been rolled out for everyone?
Sindre Olsen 0 Reputation points

2024-06-10T07:53:33.1933333+00:00

Hi, experiencing issues with templateregistrations and sends after following the migration steps.

Does anyone know if the fix has been rolled out for north europe?

Previously used templateregistrations (not installation) so I want to keep doing that.
I have checked the structure of the template and it should be correct.
The docs for templateregistration with the new v1 is not updated at all.

Here is an example that fails:
var messageTemplate = JsonConvert.SerializeObject(new

{

message = new{

notification = new{

title = "ExorLive",

body = "$(message)"

},

data = new{

appdestination = "$(action)"

}

}

});

registration = await _hub.CreateFcmV1TemplateRegistrationAsync(deviceRegistration.Handle,messageTemplate);

registration.Tags = new HashSet<string>(deviceRegistration.Tags);

Test send:
var payload = new Dictionary<string, string>

{

{ "message", "Test" },

{ "action", "messages" }

};

var outcome = await _hub.SendTemplateNotificationAsync(payload, "userId_12345");

Would be really helpful if anyone would share a working solution for using the CreateFcmV1TemplateRegistrationAsync.

Accepted answer

ajkuma 23,641 Reputation points Microsoft Employee

2024-05-14T18:40:22.3+00:00

To post an update:

Our engineering team have completed the bug fix and will begin rolling this update today. It will be deployed to all the regions in a phased manner. However, we don't have a concrete ETA to provide for the deployment of the update across all regions.

We value your patience and cooperation throughout this process.
I completely understand the inconvenience this has caused, and I extend our sincere apologies for the trouble it has brought about.
Please sign in to rate this answer.

1 person found this answer helpful.
Smitha Kalluparambil 80 Reputation points

2024-05-16T14:07:27.7033333+00:00

We did see some emails out indicating update on MS side. @ajkuma do we have to download the new SDK for this bug fix or are they server updates on your end? Or do we just run with the SDK we downloaded earlier this month for Push notifications?

Sir Jimmy 0 Reputation points

2024-05-21T20:18:10.93+00:00

I still have identical problem as described in thread, is the solution ready and deployed to all regions? It's been a week since your response @ajkuma

Smitha Kalluparambil 80 Reputation points

2024-05-21T20:27:25.77+00:00

The new SDK is now working for me with the changes deployed by MS.

I am able to send templated notifications using the new SDK and bug fix.

our code is in production and working now.

ajkuma 23,641 Reputation points Microsoft Employee

2024-05-22T17:54:04.2866667+00:00

Smitha, Glad to know that it's working. Much appreciate your follow-up and update.

tomo-kato 5 Reputation points

2024-05-23T01:30:54.4933333+00:00

Azure Notification Hubs test send still fails.

The test result will be returned as 0 for both success and failure.

Will this be fixed?

Andreas Leitel 40 Reputation points

2024-05-23T10:49:18.3066667+00:00

@Smitha Kalluparambil : What is "The new SDK" you are referring to. I can't find a new Version of Microsoft.Azure.NotificationHubs. The latestest one is still 4.2.0.

Smitha Kalluparambil 80 Reputation points

2024-05-23T12:46:38+00:00

@Andreas Leitel MS made server side changes on their end. there is no new nuget package. its the same version of SDK. 4.2.0

We tested the app in stage by setting istestEnabled = false and got the notification on the test device with a status of Enqueued

We used powershell to send out templated notification. Then we used our .net code to test the same and got a notification.

$client = [Microsoft.Azure.NotificationHubs.NotificationHubClient]::CreateClientFromConnectionString($cn,"username",$false) $installation = $client.GetInstallation('XXXXX'); $templateParameterDictionary = New-Object 'System.Collections.Generic.Dictionary[[string], [string]]' $templateParameterDictionary.Add("message", "This is a test messge. Please ignore.") $NotificationOutcome = $client.SendTemplateNotificationAsync( $templateParameterDictionary, '$InstallationId:{XXXX}').Result $NotificationOutcome

Then we pushed our code changes to point to new template and code change for Gcm to FcmV1 to PROD.

Tested out one installation id using powershell and then the our new code (with the 4.2 SDK)

Hope this helps.

Andreas Leitel 40 Reputation points

2024-05-23T17:32:54.9733333+00:00

@Smitha Kalluparambil
First - thanks a lot!

The point is, we did now basically what you did... going back to the basics by sending a very, very simple message - and by doing so, we were able to send simple templated notifications. So far so good.

The second problem that prevented us from sending a bit more complex notifications was a "migration/backward compatibility" issue. With "FCM legacy", the "data" payload was allowed to contain nested child "data" objects such as :

"notification": {...} "data": { nestedData:{ property1: "${PROP1}" property2: "${PROP2}" } }

With FCMv1 this doesn't work any more. The exact reason isn't known. Either the template parsing changed at NotificationHub or Google Firebase FCMv1 doesn't allow such nested structures any more.

The solution is to flatten those nested structures.

We didn't find any "breaking changes" documentation about that "nesting data" thing, neither at google nor at MS.

Dick Nagtegaal - de Vries 15 Reputation points

2024-05-27T06:56:42.47+00:00

@Smitha Kalluparambil : I only see you mention that you are able to send FCMv1 templated messages. But are you also able to send Test/debug messages? Are you able to send with isTestEnabled=true?

Because, if I understand @ajkuma correctly, that is what the bugfix should fix. Sending with isTestEnabled = false was already working before a fix was mentioned.

@ajkuma : Did I understand that correctly? Is the fix you mentioned supposed to fix sending messages with isTestEnabled=true? And also to be able to send test messages from the NotificationHub GUI? Is the fix rolled out yet to all regions?

I'm still unable to successfully send a message to an FCMv1 template installation with the &test tag in the REST API's querystring.

If the bug fix wasn't supposed to fix sending test messages, what does it fix?

Smitha Kalluparambil 80 Reputation points

2024-05-28T12:42:54.7433333+00:00

@Dick Nagtegaal - de Vries Earlier before this bug fix, even after IsTestEnabled = false, i was not able to get a notification. So i changed my code to now have IsTestEnabled = false for good.

srilatha cingireddy 0 Reputation points

2024-05-29T13:50:54.9066667+00:00

@Smitha Kalluparambil We have this issue still exists for us, as MS mentioned this as phase wise roll out, can you please help on the region where you have your notification hub where the fix is working?

Smitha Kalluparambil 80 Reputation points

2024-05-29T14:22:13.9333333+00:00

@srilatha cingireddy EastUS

Graeme English 106 Reputation points

2024-05-29T15:24:01.8+00:00

Is there any way to determine whether this fix has been deployed to a Hub?

We still see this problem (North Europe), it does seem to be intermittent however.

Dick Nagtegaal - de Vries 15 Reputation points

2024-05-29T17:12:27.3233333+00:00

What exactly is the bug that has been fixed? Should the bug make it possible to do a templated send using EnableTestSend = true?

srilatha cingireddy 0 Reputation points

2024-05-30T04:04:07.2533333+00:00

@Smitha Kalluparambil Thank you! The fix should be SendTemplateNotificationAsync working as is for FCM v1 without any modifications? like it is use for FCM Legacy

srilatha cingireddy 0 Reputation points

2024-05-30T04:08:00.8+00:00

@Smitha Kalluparambil Thank you! the fix should be SendTemplateNotificationAsync should support FCM v1 as is the way it use to support FCM Legacy right? Like without any modifications

Smitha Kalluparambil 80 Reputation points

2024-05-30T12:29:41.76+00:00

@srilatha cingireddy you have to update to the latest sdk and change the template to the new template.

Graeme English 106 Reputation points

2024-05-30T14:35:28.9333333+00:00

Having gone through 2 rounds of testing on pre-production environments we only hit the problem after rolling out to our production environment.

Our setup seems to be very similar to the OP's where we've updated all our existing GCM installations to FCMV1 using a powershell script. Whenever we include one of the templates in a tagExpression no matches are found e.g. "mytemplate && user:123" does not work but "user:123" does.

We seem to have found a workaround that works in our case.

Taking the OP's tag expression:

var tagExpression = "t-incident && env:dev && principal:C4E4CEB3-0E0D-446A-B5CF-73B2957745C0 && version:V4"

and changing it to the following (where xxx can be any string not previously used as a tag):

var tagExpression = "(t-incident||xxx) && env:dev && principal:C4E4CEB3-0E0D-446A-B5CF-73B2957745C0 && version:V4"

Subsequent send template notification requests now succeed in generating notifications

srilatha cingireddy 0 Reputation points

2024-05-30T17:55:14.7933333+00:00

@Smitha Kalluparambil Thank you for the response. Below is the way we have implemented for FCM which is not supported by FCM v1. Not sure what is the change in the template which is referred. we are not using any tag expressions rather only tags.

Smitha Kalluparambil 80 Reputation points

2024-05-30T18:41:10.1566667+00:00

@srilatha cingireddy

Where you are creating instance of new AzureInstallation() and assigning the templates and platform to it you also assign the template. Look up the template and change it to the new one. check this one https://firebase.google.com/docs/cloud-messaging/migrate-v1#example-simple-notification-message

var azureInstallation = new AzureInstallation

{

InstallationId = "", Platform = FcmV1,

Templates = (HERE)

};

Brad Burrick 0 Reputation points

2024-06-07T13:44:29.5166667+00:00

We were able to get this working but had to take everything out of the "Notification" object beside the title and body. Will support for "sound" and "notification_priority" be added to the "Notification" object?
Sign in to comment

1 additional answer

srilatha cingireddy 0 Reputation points

2024-06-10T11:03:37.7466667+00:00

Issue is solved for us, able to use below implementation without any change from client side.

Only change from Server side is installation of devices using the platform FCMv1 and change in the body for the message template. Below is the modified request from server for installation. Highlighted in bold are the changes.

{

"platform": "FcmV1",

"pushChannel": "$pushChannel",

"installationId": "$installationId",

"pushChannelExpired": false,

"expirationTime": "9999-12-31T23:59:59.9999999Z",

"tags": [

"$installationId"

],

"templates": {

"MessageTemplate": {

"body": "{\"message\":{\"notification\":{\"title\":\"$(title)\",\"body\":\"$(body)\"}}}",

"tags": [

"MessageTemplate"

]

}

}

}@Smitha Kalluparambil Thank you so much!!
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Share via

PushNotifications: Upgrade to FCMv1 is not delivering Templated Notifications from Azure

1 additional answer