SF-3816 Fix error being logged when a user has an invalid token#3980
Open
pmachapman wants to merge 1 commit into
Open
SF-3816 Fix error being logged when a user has an invalid token#3980pmachapman wants to merge 1 commit into
pmachapman wants to merge 1 commit into
Conversation
pmachapman
temporarily deployed
to
screenshot_diff
GitHub Actions
Inactive
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3980 +/- ##
=======================================
Coverage 81.03% 81.03%
=======================================
Files 645 645
Lines 41463 41466 +3
Branches 6750 6732 -18
=======================================
+ Hits 33600 33603 +3
- Misses 6755 6768 +13
+ Partials 1108 1095 -13 ☔ View full report in Codecov by Harness. |
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
1 participant
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.
I have marked this PR as not requiring testing, as it should be tested by a developer because it requires modifying your Auth0 profile (by clearing your device tokens in Auth0) to recreate the issue.
This change is