This repository has been archived by the owner on Apr 17, 2023. It is now read-only.
Avoid to refrehs push token when it does not exists yet #213
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@danielpassos Is starting app enough to verify this or I should send push notification? |
|
I notice that registration is not saved as before. Debugging that now. |
|
@wtrocki I have added a refresh token button in example app |
wtrocki
approved these changes
Apr 30, 2018
wtrocki
approved these changes
Apr 30, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TL:DR Firebase is calling the onTokenRefresh() on the first time we call getToken() forcing the lib to refresh a token how does not exist yet.
Related issues: