Closed timanrebel closed 10 years ago
Great! :D
Question: Why not keep the name of addPushDeviceToken and the signature of initWithToken the same, for platform parity?
Because the 2 situations are different.
On iOS you get a device token from iOS, which you give to MixPanel by calling addPushDeviceToken
, after you have registered for Push Notifications.
On Android you have to give your Google sender id (a kind of API key) to MixPanel by calling initPushHandling
, so MixPanel can register for Push Notifications and handle the rest.
addPushDeviceToken
is still present in the Android version of the module for parity, but only outputs a debug line in the log.
This difference got me confused and was why it was not working. I was sending the Android device token after registering with GCM to MixPanel, instead of handing them my sender id, so they could do it for me
Okay, now I'm with you.
I think I'd still prefer to see initWithToken
untouched though, since push registration calls should be made after any additional identify
-calls.
Also, some change log entries would be great! (:
Here you go
Awesome! Great that you updated the example file. Add the new binary as well and I'll pull. (:
Thank you! :D
Registration of Android GCM was not working. Updated code and README documentation