You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Sending a single Push creates multiple calls on server #453
I've managed to send a Push Notifications with the parse-server. I did it testing from a curl and from a custom function that I made. The push arrives correctly to the device (iPhone), but the thing is that if I do a heroku logs -t, looks like it tries like a million times to send the push.
changed the title [-]Push Notifications does multiple calls[/-][+]Sending a single Push makes the server to try like a million times to finally send it[/+]on Feb 16, 2016
changed the title [-]Sending a single Push makes the server to try like a million times to finally send it[/-][+]Sending a single Push creates multiple calls on server[/+]on Feb 16, 2016
Hi @alariju, most of time this means some of your installations' deviceToken is not valid. As we mentioned in wiki, we do not have error handling yet. If your device can receive the notification in the end, you can ignore it right now, we will add the error handling later.
@gfosco I had multiple records on _Installation class. I guess the server was iterating over all records (I migrated the _Installation class from Parse to a mongolab database.), so thats the reason all the errors were coming out in console.
@wangmengyan95 Ok, I'll be waiting for that error handling.
Activity
[-]Push Notifications does multiple calls[/-][+]Sending a single Push makes the server to try like a million times to finally send it[/+][-]Sending a single Push makes the server to try like a million times to finally send it[/-][+]Sending a single Push creates multiple calls on server[/+]gfosco commentedon Feb 16, 2016
How many records do you have in the _Installation class?
wangmengyan95 commentedon Feb 16, 2016
Hi @alariju, most of time this means some of your installations'
deviceTokenis not valid. As we mentioned in wiki, we do not have error handling yet. If your device can receive the notification in the end, you can ignore it right now, we will add the error handling later.alariju commentedon Feb 16, 2016
Thanks for the replies.
@gfosco I had multiple records on _Installation class. I guess the server was iterating over all records (I migrated the _Installation class from Parse to a mongolab database.), so thats the reason all the errors were coming out in console.
@wangmengyan95 Ok, I'll be waiting for that error handling.