404 error from push notification API

[anelezeravla]

Hello,
Our app is in production now and we are experincing some trouble with push notifications. Currently we get from our database what devices are the ones that need to receive the notification. After that, one by one, the message is prepared and the API request is made. The first requests work fine, but when it reaches a certain number, we start to get 404 error.

Is this caused by some limit on the number of times API requests are made on a certain amount of time? Would it be better to group the requests to the notification API by grouping in each request several devices?

Thank you very much,

[Kateryna Grynko]

Hi Elena,

What is the number of requests? Do you send Push notifications via Appery.io UI (https://appery.io/push) ?

[anelezeravla]

We have an estimation of more than 300 requests in one minute.

[Kateryna Grynko]

Elena,

There seems to be a bug when you send more than 300 notifications. Will be fixed in middle April release.

[anelezeravla]

Thank you very much, Katya. This is a problem for us, our app is in production now, so if it's going to take two weeks to be solved we will have to look for another provider to get a solution.

[Maryna Brodina]

Hello!

Let me check if can do something else here...

[Kateryna Grynko]

Hi Elena,

For now, you can try this workaround: do not send instant Push notifications, and add scheduled time for at least +1 minute of the current time.

This should not be costly, and notifications will be sent correctly.

You can make the following changes in the code:

1. Remove the parameter code“status”:”sent"/code.

2. Add code“schedule”: {"scheduledTime":"2013-12-13 13:44:00.000","timeZone":"180”}/code specifying the time and correct timeZone, where a notification will be sent.

   Find this in our documentation: http://docs.appery.io/documentation/b...

[vcalero]

Thanks Katya!

The workarround work fine.