Fixed a bug that occurred when handling NoneType. #677
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.
A runtime error was found while testing by linking between the VCX library in the indy-sdk repository and Aries cloudagent.
That is, the problem occurred because the value of 'non_revoked' field was not initialized to '{}' and the value was set to 'None'.
This occurs when the value of the 'non_revoked' field in the presentation record is loaded in the process of sending presentation (/present-proof/records/{pres_ex_id}/send-presentation REST API).
When a presentation proof is requested using the VCX library, the 'non_revoked' field value in the record is set to the 'None' value.
So, you can see that the return value of the dict.get() function is set to 'None' instead of '{}'.
So, it works normally only when the part that checks the field is strengthened as follows.