azure-notificationhub

Azure Notification Hub - Limit on registrations

烂漫一生 提交于 2019-12-02 11:52:43
What is the limit on registrations to cause a 403 for register create/update? According to the documentation, registration create/update ( http://msdn.microsoft.com/en-us/library/azure/dn223265.aspx ) may return a 403. So there must be some kind of limit, though I'm not sure what the limit is. The pricing page does not say anything about a registration limit. the error per the api spec is below 403 Quota exceeded; too many registrations in this namespace. Registration not created what causes the 403? Any help appreciated. Number of registrations is not limited. There is a throttling for CRUD

How to update Expiration Time in Azure Notification Hub registration?

瘦欲@ 提交于 2019-12-02 08:49:45
I've been working with Azure Notification Hubs for awhile. However, I created a new Notification Hub for a new project and I've noticed some very odd behavior. Whenever I create a registration its ExpirationDate is set to 12/31/9999 7:59:59 . So, for some, I suppose this may be a benefit, but I'd like to expire mine after a certain period of inactivity. I looked through the RegistrationDescription object and found an ExpirationTime but it's read only... How do I set this? Is this just a bug in Azure? Maybe a flag I'm missing from Azure configuration? You can do that, but on hub level, not on

Azure notification hub tags not creating nor updating - to target specific user

爱⌒轻易说出口 提交于 2019-12-02 05:06:14
问题 Hi I am working on web api as back-end service where I am using Azure notification hub. I need to notify logged in user according to conditional business logic, in short target specific user. I extract code from this article. Everything works fine but tags is not creating nor updating . I need help. Here is my code snippet // It returns registrationId public async Task<OperationResult<string>> GetRegistrationIdAsync(string handle) { ........ } // actual device registration and tag update

NotificationHubUnauthorizedException: Unauthorized on Azure Notification Hub registration

断了今生、忘了曾经 提交于 2019-12-01 21:28:01
So I'm trying the Notification Hubs on Azure. I have set things up according to this blog post . I have done the GCM setup in my Android code so I have a valid regId: String connectionString = "Endpoint=sb://<MYNAMESPACE>.servicebus.windows.net/;SharedAccessKeyName=DefaultListenSharedAccessSignature;SharedAccessKey=<MYKEY>"; hub = new NotificationHub("<MYHUB>", connectionString, this); hub.register(regid, "myTag"); So I get: com.microsoft.windowsazure.messaging.NotificationHubUnauthorizedException: Unauthorized on the hub.register method call. Any ideas? Unfortunately there is a bug in the

Diagnosing dropped notifications from Azure Notification Hub to APNS

给你一囗甜甜゛ 提交于 2019-12-01 17:57:31
问题 We have a (mostly) successful implementation of push notifications to iOS and Android devices through Azure Notification Hubs. The problem is that some of the iOS devices are apparently never receiving notifications that are sent by Azure Notification Hubs. We use templates and tags to direct the messages to the appropriate devices. The tags are interest topics, and never user-specific, so we're expecting one notification for a tag to be pushed to all devices subscribed to that tag. The

Diagnosing dropped notifications from Azure Notification Hub to APNS

狂风中的少年 提交于 2019-12-01 17:49:10
We have a (mostly) successful implementation of push notifications to iOS and Android devices through Azure Notification Hubs. The problem is that some of the iOS devices are apparently never receiving notifications that are sent by Azure Notification Hubs. We use templates and tags to direct the messages to the appropriate devices. The tags are interest topics, and never user-specific, so we're expecting one notification for a tag to be pushed to all devices subscribed to that tag. The Android devices seem to receive their notifications flawlessly, but the iOS devices are not consistent. Most

Getting QuotaExceededException - What are the operation quota limitations for Azure Notification Hubs?

|▌冷眼眸甩不掉的悲伤 提交于 2019-12-01 11:33:52
I was doing some latency/performance testing for sending push notifications with Azure Notification Hub by consecutively sending many notifications in a foreach loop. It worked fine for 100 "SendNotification" requests, altough it was relatively slow (14s), but I got a QuotaExceededException for 1000 requests in a row: [QuotaExceededException: The remote server returned an error: (403) Forbidden. The request was terminated because the namespace pushnotification-testing is being throttled. Please wait 60 seconds and try again. TrackingId:... Even when I don't wait for 60 seconds as advised, I

Getting QuotaExceededException - What are the operation quota limitations for Azure Notification Hubs?

一曲冷凌霜 提交于 2019-12-01 08:30:39
问题 I was doing some latency/performance testing for sending push notifications with Azure Notification Hub by consecutively sending many notifications in a foreach loop. It worked fine for 100 "SendNotification" requests, altough it was relatively slow (14s), but I got a QuotaExceededException for 1000 requests in a row: [QuotaExceededException: The remote server returned an error: (403) Forbidden. The request was terminated because the namespace pushnotification-testing is being throttled.

Adding Google GCM Api Key Azure Notification Hub Error

会有一股神秘感。 提交于 2019-12-01 08:14:10
We are trying to add our GCM API key to the azure notification hub and we are receiving the following error: SubCode=40000. Failed to validate credentials with GCM. Error is The remote server returned an error: (401) Unauthorized...TrackingId:410c0e33-0c38-1823-8a62-2519627c76a2_M1_G19,TimeStamp:9/19/2014 10:08:32 AM We have setup our GCM API key to allow any IP address and we have also tried registering from code like below but with the same error: NamespaceManager mgr = NamespaceManager.CreateFromConnectionString(conn); var hub = mgr.GetNotificationHub("<hubname>"); hub.GcmCredential = new

NotificationHub Push Notification returns : The Token obtained from the Token Provider is wrong

一笑奈何 提交于 2019-12-01 08:11:09
I have Wp8.1 Silverlight app that receives push notification (WNS) from Mobileservice (the old azure service). I therefore wanted to update to the new service because of the new features. I have now created/upgraded a new server to use App Service - Mobile App. And tested push notification with the sample app from azure (everything works). Going back to my app WP8.1 -> Adding the new package Microsoft.Azure.Mobile.Client through NuGet (2.0.1), there is the issue that the Microsoft.WindowsAzure.Mobile.Ext does not contain the 'GetPush' extension. It seems like it is missing it? looking to the