Fix/1188 Added allowed class for NSKeyedUnarchiver #1194
Merged
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
maratal
requested review from
lawrence-forooghian,
lukasz-szyszkowski and
QuintinWillison
lukasz-szyszkowski
approved these changes
Oct 25, 2021
lawrence-forooghian
approved these changes
Nov 3, 2021
|
Think this is ready to go? @lukasz-szyszkowski |
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.
NSKeyedUnarchiverbecomes more tricky with new version of iOS SDK. So it took a little while to figure out how to use it properly. With iOS 11 it is not happy if you indirectly allow to parse any type within an archive, so now it requires to provide allowed classes list. So I did.Also I've provided dedicated test for unarchiving function specifically in Objective-C so Swift wouldn't interfere with its under the hood collection types conversions.