-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sending push notifications with 40k installations fails #4242
Comments
Can’t you provide the logs when running with VERBOSE=1? Do you have proper indexes in place? |
@flovilmart included log with push request and response. The only index I have on the Installation record is |
There should be more logs than that, notably from the push adapter |
Sorry forgot to include that. For all the successful pushes I am seeing |
There should be the detailed error message as well, wether it’s a bad payload or a bad device token. |
After simplifying the payload by removing the chpIncident param (which should not be there in the first place) I am receiving more notifications on my device. I didn't have any problems sending that large of a payload when the push query only targeted my device. |
Ok, I just noticed this error in the log which I have never seen before:
|
Just to rewind a bit, sending a simple payload to a channels target works correctly? |
Yes. Now that I have simplified the payload I can see more pushes coming in and the push adapter always logs whether it was a successful push or a failed push. While I was sending the large payload I would never see the push adapter log so I wonder if it was just silently failing? Regarding the issue above, I think I found the solution in issue #90 |
Perhaps APNS was not happy with those large payloads, or the node apn module don’t support those properly. |
Issue Description
I have a background job on my parse instance which fetches an XML feed every 1 minute and sends a push notification to a specific channel every time it detects new data from the feed. I have noticed that sometimes the push is sent and sometimes it is not sent. On all cases I see that the success block is called but when I look in the parse-dashboard I see the push in the sending state.
Since I have no problem receiving push notifications on my dev instance (which only has 6 installations), on my prod instance I suspected this had to do with the fact that I am querying 40k installations where each channels record may contain 20 channels.
To prove the number of installations was the issue, I passed a query in the push request instead of using channels which would force the push to only be sent to my device
This query made every push a success to my device but if I remove the query and use channels instead no pushes are received. Note that although there are 40k installations, not all of them subscribe to notifications.
Steps to reproduce
Send a push to a channel observed by multiple Installation objects.
Expected Results
The push gets sent to all users.
Actual Outcome
The push notification does not get sent.
Environment Setup
Server
Database
Logs/Trace
The text was updated successfully, but these errors were encountered: