Azure Notification Hubs
An Azure service that is used to send push notifications to all major platforms from the cloud or on-premises environments.
168 questions
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I had my notification client registered and was able to send notifications normally, suddenly, I tried again and I am getting this all the time (tried many times over 4 hours period):
Error code: GatewayTimeout
Message: The gateway did not receive a response from 'Microsoft.NotificationHubs' within the specified time period.
I tried to send from the portal, VS2k19, and the console, nothing has arrived.
What is the possible problem?
Same problem here, using Visual Studio 2019 and developing an Android App on Xamarin. Android target Frame 10.0 (Q).
Also having the same issue after following the instructions for this tutorial.
does it happen in one specific notification hub? I.e. if try to create new notification hub and send test push notification from there - will it still happen?
I'm getting it when using azure portal test send on an existing notification hub and also one I just created.
Yes I tried creating a new notification hub and got the same error again.
Ran into the same problem over the weekend. At some point in the last couple of days, push notifications started failing in two different notification hubs. The error is the same - always a 60 second timeout.
Interestingly, I also tested this in a test environment where my Apple developer account is expired and I got an immediate response back saying the credentials are bad. Trying an android message in that environment results in the same timeout error as my other two environments.
The notifications fail from my app, visual studio's test tool and the test tool in the azure portal.
I also have the same problem and its extremely annoying with little to no information online... :(
Thank you for sharing this with us and we apologize for the frustration you have encountered. We have reached out internally to see if this is a known issue and what the next steps are. Once we have an update to share, we'll post it here.
Just wanted to provide a quick update that the product group is investigating these errors right now. We will share more update as we receive them.
Same issue here. Was able to verify APNS using Pusher so it appears certs and app are working properly.
This is making me question our decision to go with Azure Notification Hub. The SLA for paid subscription is 99.9% yet it has not worked for 4 days now. If this is a system wide issue, why isn't there any outage details anywhere?
We are also experiencing this issue with a brand new notification HUB
I've also created a brand new notification Hub, added my server key for Google, Hit test send, got this same error. I am however able to send push notifications in Firebase.
I even created a brand new subscription under a new account - still no go. This seems to be a system wide issue yet there's not much noise around it.... makes me wonder how well is this product supported... we're in the middle of migrating from appcenter.
Same problem. Been messing with this for days and just found this post..
Hopefully the problem can be resoled soon
Sign in to comment
Hello All, the product group believes they located the issue and took action to resolve it. We are receiving successful reports from customers.
We apologize for the impact that this caused and thank you for your patience as the product group worked towards resolving this matter.
Thank you for taking care of it! Its back to normal!
Seems that this issue is happening again.
Our notification hubs are timing out across multiple subscriptions
Hello.
I'm having issues trying to send a test notification with this message:
{"error":{"code":"GatewayTimeout","message":"The gateway did not receive a response from 'Microsoft.NotificationHubs' within the specified time period."}}
I'm sendind directly from portal dashboard and no clue on how to solve this.
Sign in to comment
4 additional answers
Sort by: Most helpful
I received this message from Microsoft, and it's working for me now.
I don't get the error anymore and it says that the notification was successfully sent but it doesn't get throught firebase. I tried romoving the Firebase Server Key and creating a new one and I used it in a new Azure Hub but it didn't work, I get a success message but the notification doesn't reach the client App. If I send it directly from Firebase it works as expected.
i had the same issue,
so I forced the device to registered again (removed the storage), and tried to send the message and was successful.
Sign in to comment
Something must've changed this is working for me now as well.
Sign in to comment
Hi Team,
All existing notification hubs are not sending notifications. Everything got failed with Timeout exception.
Now all notifications are going out.
Sign in to comment
Wondering if this is an issue again?
Noticing today (and over the weekend) that some push notifications are timing out while others are taking 30+ seconds to complete.
Sign in to comment
Activity