[PP-568] Adds an explicit logging code to track failed login error #358
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
Merge develop branch into main, version 1.0.26
Version 1.0.27
Merge develop into main version 1.0.28
Merge develop into main version 1.0.29
Merge develop into main version 1.0.30
Merge develop into main version 1.0.31
Merge develop into main version 1.0.32
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What's this do?
Adds an explicit logging code to track failed login error that appears to be triggered by the DRM.
Why are we doing this? (w/ Notion link if applicable)
https://ebce-lyrasis.atlassian.net/browse/PP-568
How should this be tested? / Do these changes have associated tests?
This issue is difficult to recreate, this logging will allow us to filter events in Firebase using error code 1005
Dependencies for merging? Releasing to production?
N/A
Does this include changes that require a new Palace build for QA?
No
Has the application documentation been updated for these changes?
N/A
Did someone actually run this code to verify it works?
@mauricecarrier7