question

BahaMasoud-0939 avatar image
5 Votes"
BahaMasoud-0939 asked AdminLimolane-5759 commented

Send a test push notification. Error Code: GatewayTimeout

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?

azure-notification-hubs
· 16
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

We have asked this customer to reach out to us offline. If you have this error as well or a solution to suggest, please continue the discussion on here.

3 Votes 3 ·

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.

3 Votes 3 ·

I also have the same problem and its extremely annoying with little to no information online... :(

1 Vote 1 ·

Same problem here, using Visual Studio 2019 and developing an Android App on Xamarin. Android target Frame 10.0 (Q).

2 Votes 2 ·

Also having the same issue after following the instructions for this tutorial.


2 Votes 2 ·

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?

2 Votes 2 ·

Yes I tried creating a new notification hub and got the same error again.

1 Vote 1 ·
Show more comments
brtrach-MSFT avatar image
1 Vote"
brtrach-MSFT answered AdminLimolane-5759 commented

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.

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you for taking care of it! Its back to normal!

1 Vote 1 ·

Seems that this issue is happening again.

Our notification hubs are timing out across multiple subscriptions

0 Votes 0 ·

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.

0 Votes 0 ·
BahaMasoud-0939 avatar image
0 Votes"
BahaMasoud-0939 answered BahaMasoud-0939 commented

I received this message from Microsoft, and it's working for me now.

The product team let us know that the issue should be mitigated. Could you try it out and let me know if it is successful?

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

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.

0 Votes 0 ·

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.

0 Votes 0 ·
JonNichols-7093 avatar image
0 Votes"
JonNichols-7093 answered

Something must've changed this is working for me now as well.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

RamakrishnaSriramoju-9000 avatar image
0 Votes"
RamakrishnaSriramoju-9000 answered RamakrishnaSriramoju-9000 commented

Hi Team,
All existing notification hubs are not sending notifications. Everything got failed with Timeout exception.

94867-screen-shot-2021-05-08-at-12123-pm.png






· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Now all notifications are going out. 95587-screen-shot-2021-05-11-at-72044-pm.png


0 Votes 0 ·
dsav-1272 avatar image
0 Votes"
dsav-1272 answered

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.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.