locked
Test Send results in 400 - Bad Request RRS feed

  • Question

  • After setting up my app with Baidu Push, signing up for an Azure Account, and adding the Baidu API key and Secret key to my Azure portal, and adding the connection string to my app, I attempted to send a Test Send from the Azure Dashboard. It resulted in a 400 - Bad Request error. Unfortunately it does not provide much more information to me than that. What could be the possible causes of this?
    Wednesday, February 22, 2017 8:13 AM

Answers

  • Hi, do you mind checking to make sure the device registrations are successful (https://docs.microsoft.com/en-us/azure/notification-hubs/notification-hubs-push-notification-fixer will be helpful)? And I'd love to take a look at the test send payload as it's likely something is off with the payload.

    • Marked as answer by StatonE Thursday, March 2, 2017 6:20 AM
    Wednesday, February 22, 2017 7:04 PM

All replies

  • Hi, do you mind checking to make sure the device registrations are successful (https://docs.microsoft.com/en-us/azure/notification-hubs/notification-hubs-push-notification-fixer will be helpful)? And I'd love to take a look at the test send payload as it's likely something is off with the payload.

    • Marked as answer by StatonE Thursday, March 2, 2017 6:20 AM
    Wednesday, February 22, 2017 7:04 PM
  • I solved this a while ago, but you were right, it was a problem with the payload. I used the Android option, but that option really just uses the GCM/FCM payload format. The format for Baidu is different, so I had to select the custom payload option

    • Edited by StatonE Thursday, March 2, 2017 6:20 AM
    Thursday, March 2, 2017 6:18 AM