Closed sfcal99 closed 9 years ago
We don't suggest using these together, however they should function as long as you are using the most recent version of each.
Looks as though the PushNotifications ANE you have is old.
May I ask why you are using both?
I just move in to Parse, perviously I use PushNotifications ANE to get the device token and manually do the push notification. Can I get the device token by only using Parse ANE? And able to do the push notification manually?
You should be able to use them together, it's just not suggested. You may end up with double notifications. We suggest if you are moving to Parse to completely move your notifications system to that platform.
can I get the device token on Parse ANE?
Not currently, we could add this as a feature if it's something you really require?
yes, please add in
getDeviceToken return an empty string on Android device, please check
This is an iOS only feature.
Can add this feature into Android as well? And why Parse.service.getCurrentInstallation() is a null object?
please update on Android
Android is implemented completely differently and doesn't have access to a "device token". It's handled completely internally to the SDK and we don't have access to it.
Does this work with Push Notifications Extension com.distriqt.extension.pushnotifications.PushNotifications
I have try to put both extension together, Push Notifications Extension no working, here is the trace
[trace] PN Supported: true [trace] PN Version: 2.7.iOS.3.2 [trace] Parse Supported: true [trace] Parse Version: 1.8.iOS.1.4 [trace] Parse Notifications Enabled: true [trace] ACTIVATE [trace] parse:registering :: [trace] parse:register:success [trace] ============= SUBSCRIPTIONS ================== [trace] CHANNEL:: test_1 [trace] CHANNEL:: test_2 [trace] ============================================== [trace] parse:register:success [trace] ============= SUBSCRIPTIONS ================== [trace] CHANNEL:: test_1 [trace] CHANNEL:: test_2 [trace] ==============================================