Arbitrary NSData failed to be decoded properly #12
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
…ld then fail to be decoded properly, leaving an NSString in its place with the `DSCborBase64DataMarker` prepended. Solution: Use `dump_bytestring_base64` as opposed to `dump_bytestring_base64url`.
|
This is probably also the fix for #9 |
|
I'll release a new pod version with this. |
|
Thank you @hamchapman ! |
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.
Problem: Arbitrary NSData would seemingly be encoded properly but would then fail to be decoded properly, leaving an NSString in its place with the
DSCborBase64DataMarkerprepended.Solution: Use
dump_bytestring_base64as opposed todump_bytestring_base64url.