Encoding Hex fix #145
Merged
Encoding Hex fix #145
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
Signed-off-by: Nayanacdac <nayana.n@cdac.in>
gab-arrobo
approved these changes
Sep 24, 2024
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.
Issue:
An authentication failure occurred during the encoding of the sequence string in the GenerateAuthDataProcedure function when using the strictHex function.
Troubleshoot:
The failure was traced to the presence of a newline character generated while converting the sequence number to hex. This occurred due to the use of Sprintln in the strictHex function.
Fix:
The issue was resolved by replacing Sprintln with Sprint in the strictHex function.
Supporting Data:
invalid-sqnStr.zip