Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with expired token on Firebase Android is back? #125

Open
SamyCode opened this issue May 17, 2017 · 3 comments
Open

Issue with expired token on Firebase Android is back? #125

SamyCode opened this issue May 17, 2017 · 3 comments

Comments

@SamyCode
Copy link

Hi

On the Android implementation, we are having an issue that is supposed to be fixed. You can see issue #28 for reference. Every time that the application calls the OnRegistered method, it is always receiving the same token, an expired token. I don't see any other work around than to call the UnRegister method every time that I open the application. This is supposed to be fixed by now. We are missing something?

Please, enlight us.

Thank you

  • Sam
@benevbright
Copy link

I'm facing the same issue.
Did you find a solution? @SamyCode

@benevbright
Copy link

benevbright commented Jun 6, 2017

I'm explaining more.
At first release and deploy to the smartphone from VS is OK.
But If I rebuild and deploy again, the token is not changed but FCM said it's unregistered token which was just successed to send a push message.

One thing I hope is that it's different when user try to update their app.
I should check it, otherwise no one would have been not receiving a push message.

@benevbright
Copy link

Ah, OK.
If I do CrossPushNotification.Current.Unregister(); before new register when the app has a previous token, everything goes fine.

It resolved my issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants