Added Abandon Permissions method to Android #1425
Conversation
Added the Revoke Token method to Android only. With this method is possible to generate a new token after a logout case with revoking.
Added Revoke Token method descprition at Android Only Methods section
Updated example with the new Revoke Token method, adding a button, alert feedback and necessary calls
|
Hi @GabeConsalter PushNotification.abandonPermissions()The API will be the same for Android and iOS. |
The Revoke Token method has been renamed to Abandon Permissions method
Renamed Revoked Method to Abandon Permissions method. The method from iOS only section was removed and added a new general method section with the new method
GabeConsalter
changed the title
|
I will test it ASAP. |
|
Released in |
|
All right, thank you @Dallas62 |
|
Hi everyone! I think that there is some weird like a default behavior on Android platform. I'm talking about when I create a new RN project and after that I install FCM and react-native-push-notification with the common comands: WITHOUT one step more I CAN START TO RECEIVE NOTIFICATIONS. So, I'm new in this library but that is normal? If that's right how can i disable that default behavior and only use the @react-native-firebase/messaging listeners and send a push notification when the listeners get some notification? I tried with PushNotification.abandonPermissions() but it didn't work! |
The Abandon Permissions method makes possible to revoke the current token, generating a new one on registration.
Unregister for all remote notifications received via APNS or FCM.
In case many users could be using the same device, Abandon Permissons will be useful to prevent notifications to the previous user from the device, using it in a logout action for example.
Fixes #864