I'm getting the following error when calling CreateOrUpdateInstallationAsync:

ArgumentException: The path sb://xxxxxxxxx.servicebus.windows.net/splashnotifdev/installations/xxxxxx:xxxxxxxxxxxxx?api-version=2017-04&" contains character(s) that are not allowed by Service Bus. Entity segments can contain only letters, numbers, periods (.), hyphens (-), and underscores (_)..TrackingId:98f12ac0-c905-4a63-a68d-c77f61cdb1ad_G5,TimeStamp:6/1/2019 3:16:11 PM

Where the installationId obtained from Firebase's onSuccessListener is a token with colon in it.
The token appears to be similar to a GCM token but prefixed with a few characters and a colon, e.g. (rest of the token masked):
dTxbVurMB3E:APA91bFsadfjklasfhjdsajkfdhaslkfhdjklsafhjklasdhlhasklfhjkasfhdjlkasfhdasjkdhf

Note that I am not calling this from Android, but passing the token to a .NET backend which calls the CreateOrUpdateInstallationAsync() method. I've also tried urlencoding the token or replacing : with %3a, which only leads to an Unauthorized error (despite the SAS working correctly, e.g. for Apns registrations).

UnauthorizedAccessException: The remote server returned an error: (401) Unauthorized. Reason: 40104: Invalid authorization token audience..TrackingId:7cf7cb94-9041-486c-8ccd-72e4f1d68d40,TimeStamp:2019-06-01T15:25:41.5055837Z

Hello,
I have an issue with Microsoft.Azure.NotificationHubs v2.0.1
Under heavy usage, after 20min, I systematically get exception "System.UnauthorizedAccessException: ExpiredToken"
After investigation I found an issue in Microsoft.Azure.NotificationHubs.Auth.TokenProvider.TrySetIntoCache : there is a SlidingExpiration even though the token is absolutely expired in 20min ( Microsoft.Azure.NotificationHubs.Auth.SharedAccessSignatureTokenProvider.DefaultTokenTimeout )
So it lacks an AbsoluteExpiration with the same ExpirationDate as the token.

My logs:
EXCEPTION:System.UnauthorizedAccessException: ExpiredToken: .TrackingId:fa5e49c9-330d-4f0e-9bb8-58360f9a4e37_G7,TimeStamp:11/13/2018 4:05:33 PM at Microsoft.Azure.NotificationHubs.NotificationHubClient.SendRequestAsync(HttpRequestMessage request, String trackingId, HttpStatusCode[] successfulResponseStatuses, CancellationToken cancellationToken) at Microsoft.Azure.NotificationHubs.NotificationHubClient.SendRequestAsync(HttpRequestMessage request, String trackingId, HttpStatusCode successfulResponseStatus, CancellationToken cancellationToken) at Microsoft.Azure.NotificationHubs.NotificationHubClient.GetAllEntitiesImplAsync[TEntity](UriBuilder requestUri, String continuationToken, Int32 top, CancellationToken cancellationToken) at NotificationHub.API.BusinessCommands.RegisterMobileDeviceCommand.ExecuteAsync()

A dirty workaround until fix is to disable token caching (using Reflection):
var tokenProviderField = typeof(Microsoft.Azure.NotificationHubs.NotificationHubClient).GetField("_tokenProvider", System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.NonPublic); var tokenProvider = tokenProviderField.GetValue(client); var tokenProvider_cacheTokensField = tokenProvider .GetType() //Microsoft.Azure.NotificationHubs.Auth.SharedAccessSignatureTokenProvider .BaseType //Microsoft.Azure.NotificationHubs.Auth.TokenProvider .GetField("_cacheTokens", System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.NonPublic); tokenProvider_cacheTokensField.SetValue(tokenProvider, false);

this bug may be related to #9
I will submit a PR.
Thanks

NuGet package version 3.2.0 seems to be delay signed and not fully signed as expected. Running our application with the new package results in the error below. Running sn.exe reveals that the assembly is delay signed. Running the same verification on version 3.1.0 results in a valid assembly. Seems to be 3.2.0 specific.

Could not load file or assembly 'Microsoft.Azure.NotificationHubs' or one of its dependencies. Strong name signature could not be verified.  The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045) 

sn -vf Microsoft.Azure.NotificationHubs.dll

Microsoft (R) .NET Framework Strong Name Utility  Version 4.0.30319.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Microsoft.Azure.NotificationHubs.dll is a delay-signed or test-signed assembly

I'm unable to send a WNS notification with X-WNS-Match header to remove a notification from the Action Center. The current NotificationHubClient implementation has not any option to send the HTTP DELETE request required for this scenario.

In V3, GcmRegistrationDescription is marked as obsolete, so the SDK takes care of returning the same registration type when creating new Fcm registration.
However, when querying device registrations, GcmRegistrationDescription objects returned as REST responds with GcmRegistrationDescription content.
Shouldn't the SDK fully switch to Fcm and explicitly convert Gcm to Fcm descriptions?

Im using xamarin.forms and when i upgraded the Microsoft.Azure.NotificationHubs from 3.2.1 to 3.3 the RegisteredForRemoteNotifications(UIApplication application, NSData deviceToken) stopped being called.

Using NotificationHubClient, I want to create an installation when it doesn't exist. But when I run GetInstallation(id) and id doesn't exist, I get an exception:

Microsoft.Azure.NotificationHubs.Messaging.MessagingEntityNotFoundException: 'The remote server returned an error: (404) Not Found. Installation not found.TrackingId.

How can I check if an installation already exists without try/catching the GetInstallation() method?

Is this a bug/gap or is this a deliberate choice to exclude it?

Documentation for supported installation platform

Hi,

NotificationHubClient.CreateOrUpdateInstallation method is void, but looking to the source code it return a response, but it is not checked or return why?

Also several other method do not return any value but they could.

The example at https://github.com/Azure/azure-notificationhubs-dotnet/blob/master/Samples/SendPushSample/SendPushSample/Program.cs doesn't work.

The code is based on SDK 3, but the project imports 2.x

The example fails with:

Unhandled Exception: System.ArgumentNullException: Value cannot be null.
Program.cs:line 131

outcomeDetails = await nhClient.GetNotificationOutcomeDetailsAsync(notificationId);

Because notificationId is null.

After debugging the SDK I noticed that the code is looking for a Location header, but inspecting the HTTP response from Azure notification hub, there is no such header.

Request made by the SDK:

Response received by the SDK:

Any suggestion?

As noted in PR #15, we need to have better formatting for our HTTP mocked data. This task should run a standard JSON formatter over each of the .http files.

As far as I can see, one of your SDK samples (SendPushSample) provides apns-collapse-id header to APNS. In my case however this doesn't work as expected - notifications don't 'collapse'. Has anyone tested if these headers are passed to APNS and if behavior was correct?

I'm wondering if the type of authentication is important here in Azure Notification Hubs, since I'm using old certificate-based authentication rather than new key-based authentication.

I use the NotificationHubClient as a Singleton in my long-running service. (> 1 month)
When the DNS (IP) for the HUB changes (a few times per year) this is not reflected in the singleton NotificationHubClient (due to "new HttpClient()") and I'll get exceptions in my code and have to restart the whole service to reflect the DNS change.

What is the correct way to solve this in code right now and is there any plans to use the IHttpClientFactory to create the HttpClient instead, which also should solve the problem.

Good day, I made a SO question about this, but I have not any official MS response.

SO

What is the correct way to use the c# Azure Notification Hub Client?

We are using this in a very high usage server sending millions of pushes a day.

I would like to know if we should recreate the NotificationHubClient every time or if we should keep a static/singleton instance of it and then reuse that each time?

Currently, we recreate it every time we send a push notification. However, I know from personal experience we have had issues with the .net HTTP client and it not releasing tcp sockets fast enough. I was worried that this library could start having similar issues.

I have successfully implemented Azure Function, which sends push notifications to NotificationHub for Android, iOS and UWP. During the testing I discovered that when Android device is in Doze mode push notification is not delivered on lock screen. It is only delivered when I unlock the phone.

I found out this stackoverflow post, which helped me to fix it with method SendFcmNativeNotificationAsync. I used this code:

string payload = @"{
                    ""data"":{
                        ""notificationtype"":""sap"",
                        ""title"":""value2"",
                    },
                        ""priority"":""high""
                    }";

await hub.SendFcmNativeNotificationAsync(payload);

However my implementation using SendNotificationAsync method which works for all 3 platforms, but not in Doze mode. This is my code to send notification:

Dictionary<string, string> templateParameters = new Dictionary<string, string>();

templateParameters["alert"] = "Test";
templateParameters["title"] = "Whosap";

var notification = new TemplateNotification(templateParameters);
await hub.SendNotificationAsync(notification);

I tried to set header of notification:

var headers = new Dictionary<string, string> { { "android", @"{""priority"": ""high""}" } };
notification.Headers = headers;

But this didn't work. Does anybody know how to set priority in TemplateNotification object and send it with SendNotificationAsync method?

There is a lot of information floating around regarding the impending deprecation of GCM in favor of FCM. What does this mean for NotificationHubs .NET SDK users? We are creating/updating registrations and are sending push notifications. Do we need to switch our backend code to V3 before April 2019? Or is this handled by Azure for us?

"If you have projects that are still using the GCM APIs, you will need to update your client and server code to use FCM before April 11, 2019. But rest assured, your existing GCM tokens will continue to work with FCM so you won't lose the ability to send messages to your existing users." (https://firebase.googleblog.com/2018/04/time-to-upgrade-from-gcm-to-fcm.html)

I have the hub working using "sandbox", then I switch it to "production" mode, I see the client device gets a new registration handle id, but when I test send on azure, get the error
"The Push Notification System handle for the registration is invalid", I was using the variable "testsend" in code to check the outcome object as well, but it does not really say much.
When it is switched to "production" mode, azure hub forwards the message to the production apple push notificaiton server, and my local devices is using the correct endpoint, but use a development certificate. I am not sure what this means, does the devices need to have the app installed with appstore provision profile in order to receive a message from "production" channel?
So the only way for testing is through "testflight"?

Any help will be appreciated.
Marc

I want to use templates, Installation API and provide apns-collapse-id header to APNS for Apple notifications. Is the code below a proper way of doing so? The docs say InstallationTemplate.Headers property is for MPNS-targeted notifications, so not sure if this would work for Apple (APNS) as well.

var installation = new Installation
{
    InstallationId = "myId",
    Platform = NotificationPlatform.Apns,
    PushChannel = "xxx",
    Templates = new Dictionary<string, InstallationTemplate>
    {
        {
            "hello",
            new InstallationTemplate
            {
                Body = @"{ ""aps"": { ""alert"": ""Test"" } }",
                Headers = new Dictionary<string, string> { { "apns-collapse-id", "myCollapseId" } }
            }
        }
    }
};
await _hub.CreateOrUpdateInstallationAsync(installation);

I am registering installations from my .NET backend server code with multiple templates each. For example:

var installation = new Installation
{
    InstallationId = id,
    PushChannel = token,
    Templates = new Dictionary<string, InstallationTemplate>(),
    Tags = new List<string> { "userId:123456" },
    Platform = NotificationPlatform.Gcm
};

installation.Templates.Add("template1", new InstallationTemplate { Body = "{\"data\":{\"message\":\"$(message)\"}}"});
installation.Templates.Add("template2", new InstallationTemplate { Body = "{\"data\":{\"message2\":\"$(message)\"}}"});

await _client.CreateOrUpdateInstallationAsync(installation);

How do I target a specific template when sending a notification? All I see in the SDK is the following:

await _client.SendTemplateNotificationAsync(
    new Dictionary<string, string>
    {
        { "message",  "Hello world." }
    }, "userId:123456");

The SendTemplateNotificationAsync method does not have any parameters that let me specify which template I am targeting (for example, template2).

Which template will be used? Am I misunderstanding something here?

Hello,

I'm not quite sure, but it's been a rough day for me getting this to work since iOS 13.
I'm trying to send a test message via the Notification Hub window from the Server explorer in VS2015. I'm getting this "the push notification system handle for the registration is invalid" error.

I followed the guide and here's what I got.

I'll try to run through the guide again. I got it working before all the shebang from iOS13.

thanks

https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/sending_notification_requests_to_apns

According to Apples documentation above iOS 13 devices requires a "apns-push-type" header to be present. And leaving it out may cause delayed delivery or total loss of delivery.

So the AppleNotification class should add the below by default.
AppleNotification.Headers["apns-push-type"] = "alert"

I am trying out the new 2.0.0-preview2 available on nuget in a ASP.NET Core 2.1 application on netcoreapp2.1. This seems to work fine as a drop in replacement for 1.0.9 without any breaking changes.

In my application, NotificationHubClient is initialized as a properly of a singleton instance. I notice that after ~1 hour of the application running, any NotificationHubClient functions that are invoked no longer work. My application does not throw any errors, but all activity to my Notification Hub ceases (confirmed by looking at metrics in the Azure portal) and I no longer get push notifications to my apps. If I restart the server (causing the singleton instance to new again) things again start working for ~1 hour and then stop again.

Due to the nature of the consistent 1 hour lifetime of things working, I suspect that the NotificationHubClient instance is not renewing it's SAS token or something that has a 1 hour lifetime. To workaround this problem I now keep track of internal 30 minute timer where I new the NotificationHubClient up again every 30 minutes. Doing this resolves the problem.

Using NotificationHubClient from Azure function (the client is created on every function call) on high load fails with "System.Net.Sockets.SocketException: Cannot assign requested address"
I believe this is because new HttpClient is created instead of using the HttpClientFactory and the ports are getting consumed very quickly (the known issue of using HttpClient inside Azure functions).

Hi there,

I have an UWP Project, that is using Notificationhub.
When I compile my code in debug mode (x86) everything works fine.
When I try to create a store package the compilation fails for configuration release x86 with error:

"System.Runtime.Serialization.InvalidDataContractException: Type 'Microsoft.Azure.NotificationHubs.CDataMember' does not have a static method 'GenerateSchema' that takes a parameter of type 'System.Xml.Schema.XmlSchemaSet' as specified by the XmlSchemaProviderAttribute attribute."

I am using VS2019 Version 16.4.2
Nuget Package is: Microsoft.Azure.NotificatioHubs Version 3.3.0

What causes this isssue??

Kind regards,

Martin

I try to call CreateOrUpdateInstallationAsync in my backend service for install device, however, it would not affect correctly when the update information includes the push channel.

I use the following code to test:

        var existInstallation = await hub.GetInstallationAsync(installation.InstallationId);

        await hub.CreateOrUpdateInstallationAsync(installation);

        var updatedInstallation = await hub.GetInstallationAsync(installation.InstallationId);

        if (existInstallation.PushChannel == updatedInstallation.PushChannel && updatedInstallation.PushChannel != installation.PushChannel)
        {
            throw new Exception("Push channel update failed.");
        }

It should not throw the Exception if the push channel updated correctly.

Additionally, if I delete the installation and then install again, it can set the new push channel.

Given a configured NotificationHub with a .voip
When using test-send facility
And attempting to send the vanilla payload {"aps":{"alert":"Notification Hub test notification"}}'
Then I should see the Outcome The Notification was successfully sent to the Push Notification System

This is repeatable

Diagnosis

Having bypassed the notification hub and used curl to send the equivalent request directly to https://api.sandbox.push.apple.com:443

     --http2 \
     --header "authorization: bearer $JWT" \
     --header "apns-topic: ${BUNDLEID}" \
     --data '{"aps":{"alert":"Notification Hub test notification"}}' \ 

We got success for a the scenarios

Conclusion

The Notification Hub is interfering with the apns-push-type header

For bundle id ending .voip

A failure can be invoke by setting alert as the apns-push-type
Setting voip as the apns-push-type the issue is fixed.

     --http2 \
     --header "authorization: bearer $JWT" \
     --header "apns-topic: ${BUNDLEID}" \
     --header "apns-push-type: alert" \
     --data '{"aps":{"alert":"Notification Hub test notification"}}' \ 

Note:

This behaviour was first noticed in September 2109 around the time of the IOS 13/Xcode 11 release.

HI there,

please implement scheduled notification using templates.
This would be helpfull in muliplatform environments.

Thanks,

Martin

Multiple customers are reporting that they are unable to include headers to indicate the apns-push-type when using templates.

More conversation can be found here: #88 (comment)

For the last two days I get lots of Microsoft.Azure.NotificationHubs.Messaging.MessagingExceptions without any modification in my code. I have upgraded Microsoft.Azure.NotificationHubs to the leatest 3.2.1.0 varsion but it didn't help. Never had this kind of exceptions before

Here is a detailed exception message:

The remote server returned an error: (500) InternalServerError. Reason: 50002: Provider Internal Error..TrackingId:427adaf8-eb0a-4a8a-af86-dc5998cc4388,TimeStamp:2019-10-09T13:04:58.7861049Z

Any help would be greatly appriciated

We tried to upgrade to Microsoft.Azure.NotificationHubs 3.0.0 from 1.0.6 but our build is failing, I see Microsoft.Azure.NotificationHubs.GcmRegistrationDescription; Microsoft.Azure.NotificationHubs.NamespaceManager ; .Microsoft.Azure.NotificationHubs.NotificationHubDescription classes are missing in Microsoft.Azure.NotificationHubs 3.00 dll

This SDK contains (hopefully) full set of functions supported by Azure Notification Hubs. It's for sure a natural choice for server-side apps, but since it targets .NET Standard, it could also be used on the mobile-client side (Xamarin). Is this a good idea? Of course we're not going to use API to send notifications from there, only to register.

There are other SDKs for Xamarin, but they are just wrappers around native iOS/Android SDKs and seem to be old and not updated anymore:
https://github.com/xamarin/XamarinComponents/tree/master/XPlat/AzureMessaging

It would be great if there was a clear recommendation somewhere.

As noted in the PR #15, we have time intervals between checks such as the following:

await _hubClient.CreateOrUpdateInstallationAsync(installation);

await Task.Delay(TimeSpan.FromSeconds(1));

Assert.True(await _hubClient.InstallationExistsAsync(installationId));

This is unnecessary if we are testing against mocks, and is only applicable to when running integration tests when the Notification Hubs connection string is specified. Instead, we should have the following which delays only when running non-mocked tests.

Task Sleep(TimeSpan span)
{
    // If mocked then only return an empty task, otherwise sleep
}

We need to send both iOS "alert" pushes and "voip" pushes over the same notification hub.

Wer are using SendTemplateNotificationAsync with two different templates.
One for alerts and one for voip pushes.
We have two correct device tokens and we are also adding the required headers to the templates.

For sending voip pushes with token based authentification the "apns-topic" needs to be set to the bundleId + suffix ".voip" and the "apns-push-type" should be "voip".

We tried with TemplateRegistrations and TemplateInstallations

The BundleId in the the notification hub in the portal is configured without the ".voip" suffix.

The "alert" pushes work, but the "voip" pushes return the error "WrongToken".

If we change the BundleId in the portal to bundleId + suffix ".voip", the voip pushes work and the "alerts" stop working.

This looks like the "apns-topic" is not passed to apple or overwritten when calling their api.
When calling directly the apple api via http everything works.

Hi,

I am trying to switch from authentication mode "Certificate" to "Token". According to the documentation it should be enough to change the credentials in the azure portal.

After doing that, the "Test Send" of the portal still works as expected: the push notifications arrive on the devices.

But when using the Microsoft.Azure.NotificationHubs SDK, nothing is sent to the client.

When I set the "enableTestSend" flag while creating the NotificationHub Client (NotificationHubClient.CreateClientFromConnectionString("", "", true)), and look at the result of the SendNotificationAsync method, I get a failure for each registered apple device, saying "The Token obtained from the Token Provider is wrong".

Here is my notification body:

{
   "data":{
      "someAdditonalData":"data"
   },
   "aps":{
      "alert":"Notification Text"
   }
}

I set the following headers:

• apns-priority: 5
• apns-topic: my.bundle.id
• apns-collapse-id: 10

Further, the SDK seems to add another header: "ServiceBusNotification-Format: apple"

I don't see what I am missing here. Shouldn't my code be the same, no matter what authentication mode I use?

Thanks in advance.

Best regards

Notification Hubs now try (and fail) to infer the value for apns-push-type

No account is taken of voip bundle ids

There is also no facility in the Test Send facility to specify the apns-push-type for the test message.

This specifically breaks the debugging of VOIP notifications.

This issue happens in my integration tests. Note that I am running these tests from my local machine. However they were passing when I was on version 1.x of the nuget package. Since 2.x this has started happening.

(for simplicity I list here only the main methods - do consider that the registration id i pass in there is always the correct one)

I call:

1. CreateOrUpdateRegistrationAsync
2. DeleteRegistrationAsync
   this always passes and I never get an exception

I call:

1. CreateOrUpdateRegistrationAsync
2. SendTemplateNotificationAsync
3. DeleteRegistrationAsync
   this never passes and I get MessagingEntityNotFoundException on DeleteRegistrationAsync.

Does SendTemplateNotificationAsync method somehow deletes the invalid registration that is created in CreateOrUpdateRegistrationAsync.
In my theory - it can'f find a device then it removes the registration automatically - but I do not know. Can you please verify this?

In the old package (before the .net standard) we use to be able to do something like:

var namespacemanager = NamespaceManager.CreateFromConnectionString(connectionString);
namespacemanager.GetNotificationHubs();

I guess those "management" api were remove to the package and put into Microsoft.Azure.Management.NotificationHub. My problem with that package is that I don't see how to simply use the connectionstring.

It's kind of the same story as the one in servicebus here: Azure/azure-service-bus-dotnet#358.
But they finally decided to add back some management capabilities in Microsoft.Azure.ServiceBus using directly the connectionstring

So I guess my question is how could I get the list of NotificationHubs from the namespace connectionstring and if it's not possible yet, is there any plan/timeline to add that back to the .net standard package.

Thanks

hubClient.SendAppleNativeNotificationAsync(json, tags)

is the same as doing this

hubClient.SendNotificationAsync(new AppleNotification(json), tags);

What you need to do to get Apple to NOT drop the notification after the first deliver fails is to set a expiry time like this.

notification = new AppleNotification(json);
notification.Expiry = DateTime.UtcNow.AddMonths(1);
hubClient.SendNotificationAsync(notification, tags);

So either the default for AppleNotification.Expiry should be changed from NULL to something like DateTime.UtcNow.AddDays(1) or SendAppleNativeNotificationAsync should be deprecated as using it will cause many of you push requests to fail delivery to the devices.

Hi,

I wrote this code and run successfuly with FCM But same code didnt work Apns I've got this error.

Any idea?

bla bla bla...

` var installation = new Installation()
{
Platform = platform,
PushChannel = appInstallation.PushChannel,
PushChannelExpired = false,
InstallationId = appInstallation.InstallationId, //Sample: e26741c15c284174a3566c52323a8edd
Tags = tags,
Templates = templates

            };
            await _hub.CreateOrUpdateInstallationAsync(installation);`

Thank you.

I've upgraded my nuget package from 1.0.9 to 3.0.2 to migrate from GCM to FCM. Based on the release description, it looks like GCM methods now route through the FCM api. So is there anything in my code I need to change (e.g. can I continue to use SendGcmNativeNotification)?

I'm using version 3.0.1 in my Azure Function project. Every time I call CreateOrUpdateInstallationAsync I get an exception saying that it's trying to load Newtonsoft.Json v10. I have Newtonsoft.Json version 11.0.2 installed (and require it, I can't use a lower version). I'm not sure why I'd be getting this, since the NotificationHubs package says it requires a version of the Json lib >=10.0.3. Here's the full exception details:

Edit1: I have no idea why it's bolding some chunks, tried editing it to remove it, couldn't figure it out
Edit 2: I tried downgrading package versions, and kept getting this exact same exception until I got down to version 1.0.9. This is the latest version I'm able to use without getting an exception.

`System.IO.FileNotFoundException: Could not load file or assembly 'Newtonsoft.Json, Version=10.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.
File name: 'Newtonsoft.Json, Version=10.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'
at Microsoft.Azure.NotificationHubs.Installation.ToJson()
at Microsoft.Azure.NotificationHubs.NotificationHubClient.d__53.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at BurnableCloud.Shared.Notifications.d__12.MoveNext()

Pre-bind state information
LOG: DisplayName = Newtonsoft.Json, Version=10.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed
(Fully-specified)
LOG: Appbase = file:///C:/Users/myusernamecleverlyremoved/AppData/Local/AzureFunctionsTools/Releases/1.6.0/cli/
LOG: Initial PrivatePath = NULL
Calling assembly : Microsoft.Azure.NotificationHubs, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35.

LOG: This bind starts in LoadFrom load context.
WRN: Native image will not be probed in LoadFrom context. Native image will only be probed in default load context, like with Assembly.Load().
LOG: Using application configuration file: C:\Users\myusernamecleverlyremoved\AppData\Local\AzureFunctionsTools\Releases\1.6.0\cli\func.exe.Config
LOG: Using host configuration file:
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.
LOG: The same bind was seen before, and was failed with hr = 0x80070002.`

Hi,

Consider following scenario:
An ios device registers with an back-end API and a tag A. the back-end API makes an installation in notification hub with the tag.
An other android device registers with an back-end API and a also tag A. the back-end API makes an installation in notification hub with the tag.

Now a scheduled job is running and wants to send notifications to tag A,

The question is how can the back-end send notifications to all devices with tag A without calling both methods SendApnsNotificationAsync and SendFcmNotificationAsync to get all devices. Because at this moment the back-end has only the tag and the message nothing else, so the back-end does not know which platforms are involved. So in case only one registration would be there the second call lets say SendFcmNotificationAsync will always give an exception (Something like: No registrations found).

Hi,

for the last few days I am constantly getting System.ArgumentException exception

The Apns certificate is expired. .TrackingId:66d9de0f-7f70-4451-b7a8-344003a45da5_G6,TimeStamp:11/26/2019 8:52:24 AM The Apns certificate is expired. 

I double-checked on iTunes Connect and the certificates that are uploaded to Azure are valid (will expire in few months)

Any help on that would be appreciated

I expected this to just work (based on my previous experiences with ConnectionStringBuilder types):

using Microsoft.Azure.NotificationHubs;

var builder = new NotificationHubConnectionStringBuilder("Endpoint=sb://my-namespace.servicebus.windows.net/")
{
    SharedAccessKeyName = "DefaultFullSharedAccessSignature",
    SharedAccessKey = "<therealsecret>"
};

var connectionString = builder.ToString();

Expected
Endpoint=sb://my-namespace.servicebus.windows.net/;SharedAccessKeyName=DefaultFullSharedAccessSignature;SharedAccessKey=<therealsecret>

Actual
Microsoft.Azure.NotificationHubs.NotificationHubConnectionStringBuilder

It would be great to extract the interface, as in computer vision SDK.
This allows the end user to mock the notification client for testing.

I am attempting to diagnose a FCM notification to a single device with a channel scenario which isn't being delivered. I am trying to use 'CreateClientFromConnectionString' with 'enableTestSend' enabled. This the only method that I know of for this type of debugging, but when the notification is sent it crashes the Azure debugging instance and disconnects from VS2019. This event has been consistent since enabling the parameter.

I opened a support case which was assigned to the Azure Service Bus Team, Case 119080124004303. It was recommended that I open an issue here. The recommendation is based on the following exception which the team found:

{"level":1,"method":"System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw","assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","line":0},{"level":2,"method":"System.Threading.ExecutionContext.RunInternal","assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","line":0},{"level":3,"method":"System.Threading.ExecutionContext.Run","assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","line":0},{"level":4,"method":"System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem","assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","line":0},{"level":5,"method":"System.Threading.ThreadPoolWorkQueue.Dispatch","assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","line":0}]},{"id":65666079,"outerId":29613747,"typeName":"System.ArgumentNullException","message":"Value cannot be null.\r\nParameter name: notificationId","hasFullStack":true,"parsedStack":[{"level":0,"method":"Microsoft.Azure.NotificationHubs.NotificationHubClient+d__50.MoveNext","assembly":"Microsoft.Azure.NotificationHubs, Version=3.0.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35","line":0},{"level":1,"method":"System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw","assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","line":0},{"level":2,"method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","line":0},{"level":3,"method":"System.Runtime.CompilerServices.TaskAwaiter`1.GetResult","assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","line":0},{"level":4,"method":"NotificationService.AsynchNotification+d__13.MoveNext","assembly":"WWW, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null","fileName":"C:\Projects\IdentityCheckpoint\VS2019\IdentityCheckpoint\WWW\NotificationHandler.cs","line":158}]}],"severityLevel":"Critical"}}}
The thread 0x6c8 has exited with code 0 (0x0).

Consider following code:

var exists = await _hub.RegistrationExistsAsync(registrationId);
                if (exists)
                    await _hub.DeleteRegistrationAsync(registrationId);

I am making sure the registration exists before I try to delete it - simply to avoid MessagingEntityNotFoundException.

However RegistrationExistsAsync throws "MessagingEntityNotFoundException" - I do not see the point in that. Shouldn't it return "false" if it can't find the registration?

As far as I can see, CancellationToken can be used to cancel http calls, but it is simply removed in public overloads. What are the reasons for this? I am ready to do PR to bring it out.

We are currently using CreateRegistrationAsync works to send a payload that ends up the data property when received by an Android device. Which works fine when the app is in the foreground, but doesn't result in a push notification when the app is in background or stopped.

However, we need the payload to be:

{
  "data" :  { 
      "objectId" : 4,
      "name" : "Joe Smith"
  },
  "notification" : { 
      "title" : "This is a title",
      "body" : "And this is a body"
}

This is to match the specification from Firebase:
https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages

How can I register a template to include both "data" and "notification" keys please? I have tried just adding "notification" in my template, but it ends up being nested under "data" - rather than being a sibling.

TIA 😃

I had a notification hub & namespace configured on Azure Portal. I had 5 active devices registered as shown on the portal widget. I deleted the hub and the namespace and recreated them with the same names. The active device count still showed 5 instead of 0, so it seems deleting and re-creating the same resource does not reset everything.