-
Notifications
You must be signed in to change notification settings - Fork 880
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
Fix #1733. Force to obtain new tokens if accessToken is nil #1734
Conversation
…if accessToken is nil.
This will need a test before merging |
We'll need to understand the intent behind the original behavior. I don't immediately see why we'd call |
@palpatim Is there an estimated time? Note that is a serious bug: Our app won't work properly after this will solved. Don't hesitate to ask me if you have any doubts. Thank you! |
Any updates about this PR? |
@palpatim When do you plan to release the fix of this issue? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor point of code duplication, otherwise change LGTM. We will need to get a test in place for this, which @royjit is working on now.
After the user attribute update, Cognito clears the session. But this is not later refreshed. This change add test to catch this behavior. This test will fail until the PR #1734 is pushed.
Modifications in
GetSessionInternal
method to force to obtain new tokens if accessToken is nilIssue #, if available: #1733
Description of changes:
Retrieve access token value in order to check if it is null. In that case, we have to retrieve new tokens. This situation can happen after calling
clearSession
method.See #1733 for more information.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.