Open Niko87 opened 7 years ago
Hi, We have the same issue. After some debug, the onPushTokenReceivedCallback and onMessageReceivedCallback are not fired.
firebase.getCurrentPushToken().then((token: string) => {
// may be null if not known yet
console.log("Current push token: " + token);
});
this function retrieves correctly the token. So the init is done, and its not firebase communication issue with APNS.
and yes, its very frustrating :)
Thanks for your response, in my case this function returns null .. in 4.1.1 ..
Frustrating is has been chosen nativescript over ionic.. i don’t think the time wasted making it work (different libraries versions, angular, firebase, fresco, etc) is recompensed in any case... development was a nightmare (just because libraries don't work as expected!!!!).. and the production app its heavy, and not fast.. nativescript is overrated.. but i have to finish this app for go ahead !
The same has happened to me with push notifications. Completely agree with you. The idea of nativescript is good, but it's all very poorly documented. Each step is a little hell until you get what you need.
@AlbertoVP Would you mind channeling those frustrations into PR's to make the documentation better?
@EddyVerbruggen have you been able to reproduce this issue please ?
@Niko87 @papangproduction @EddyVerbruggen @AlbertoVP I notice that the onPushTokenReceivedCallback method is called once when the user install the app then u have to use the getCurrentPushToken and to handle the push notification just need to use the addOnMessageReceivedCallback method
Im not getting the token registration in version 4.1.1, but yes in 3.10.2.. idk why... its frustrating... the log not saying anything special... only in ios, android is working perfect...