-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Empty registrationId Android #265
Comments
@brambogaerts Don't use the senderID from Parse. Use the GCM one you had to provide to Parse. https://github.com/phonegap/phonegap-plugin-push#pushnotificationinitoptions |
@macdonst Thanks for your speedy reply. However, I have created a new app from scratch to test with, and used my own senderID I provided to Parse, and I still get the same results... |
As I was looking through the log items, I found this: |
@brambogaerts I am unable to reproduce your problem. Got a reproduction scenario/code I can look at? |
Well, the problem fixed itself. Somewhere between cleaning all kinds of caches and reinstalling every part imaginable, I managed to get the correct ID. Thanks for your response! |
Closing, re-open if you can reproduce. |
Colleague of @brambogaerts here... Since we have bad wifi reception in the space we're working we setup a wifi using OS X's Internet Sharing. Somehow this is related to this problem as we got a real registrationId when we connected to a proper router... @macdonst any idea how that could be possible? |
@thomasjonas sorry no. Networking is like black magic to me. Especially when you get into connection sharing and captive gateways. |
This thread has been automatically locked. |
I am using Parse.com to send push messages to my Ionic app. Therefore, I am using their senderID.
The onRegistration event does fire for Android, but the registrationId field is empty, so I am unable to receive push notifications.
The text was updated successfully, but these errors were encountered: