-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Sending push notifications success BUT not receiving any #840
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
Comments
i uploading my certification on onesignal site for test and it's work but this code is run and get success sent message but not showing any notification on safari |
any news? |
You mention Safari, browser push requires an encrypted & signed payload which your example doesn't do. |
Same issue. I see how many people are facing this problem and it is unbelievable there is still no good response. The case is, it is hitting the success event, but the device is not receiving any notification on iOS. Trying http://pushtry.com/ with same certificate, password, and device token receives notification without any problem. This problem should have a valid explanation, as MANY-MANY people are facing the same. |
I would now look at the payload your sending. Apple accepting it doesn't mean its able to be processed by your app, either the library or your app could be quietly eating the notification because it can't parse the payload. |
I had this problem and in my case, my payload was missing aps: {} I was sending
instead of
Thats what fixed it for me |
same issue here... getting success for both GCM and APNS but notifications are not being sent... no idea where is the problem. |
any update on this issue? same here... getting success response but notification not delivered to device, creating very uncertainty. |
Hello, You should use this server side library for push notification in c#: |
What version of PushSharp are you using?
i used version 4.0.10
Describe your issue:
Sending push notifications success BUT not receiving any
static void Main(string[] args)
{
The text was updated successfully, but these errors were encountered: