-
-
Notifications
You must be signed in to change notification settings - Fork 100
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
Push notification always says 0 sent #111
Comments
I am experiencing the same issue, Any insight would be helpful. |
I was unable to get this to work properly and had to abandon development with parse. I have moved my development to firebase. |
I did the same.
…On Mon, Apr 29, 2019 at 9:58 AM Billy Ashmall ***@***.***> wrote:
I was unable to get this to work properly and had to abandon development
with parse. I have moved my development to firebase.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#111 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA24ACOC7TX5QQDIJKL4ZK3PS35KBANCNFSM4E2DIIKA>
.
--
Chris Hampton
Each of you should use whatever gift you have received to serve others, as
faithful stewards of God’s grace in its various forms.
-1 Peter 4:10 NIV
|
It uses to happen the push's query does not match to any valid valid installation. Would you be able to share the push's query and the installation data? |
I did the same, when I check the server log I got this message: |
I try to push from an android app or from the parse dashboard and it says success, but it also says 0 notifications sent and of course i get no notifications. I have tried with GCM senderid and and key i have also tried with FCM key (senderid is the same) Exactly the same results. There are no errors even in verbose. I can post the verbose if it would help.
Here is the dashboard info:
Type | Target | Pushes Sent | Name | Time | Status
api | Everyone | 0 | anything | Apr 11, 2018, 14:37 CDT | SENT
Any ideas on what i'm missing?
The text was updated successfully, but these errors were encountered: