NetworkTasks: Don’t treat missing refresh token as fatal error#41
Merged
Conversation
This change makes it so that a refresh token is no longer required in the data returned from a network request. Some authentication services do not reply with a refresh token, making all requests fail. The change is to only assign the current locker’s refresh token if it exists in the data.
onmyway133
approved these changes
Aug 16, 2017
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This change makes it so that a refresh token is no longer required in the data returned from a network request. Some authentication services do not reply with a refresh token, making all requests fail. The change is to only assign the current locker’s refresh token if it exists in the data.