Swiftshield Versions Save

• Improved how the SWIFTSHIELDED property is added - @strfn
• Fixed SwiftShield not handling files with escaped spaces correctly - @ptwoms

• Added ignoreNames, a field of names that should not be obfuscated. @andreiChis70

Fixed Xcode 12 builds failing by @ekam123

Instance, class and global properties will now be obfuscated, with the exception of properties under types that inherit from Codable and classes exposed to Objective-C. For more information, check the limitations document.

Although we have lots of tests checking if property obfuscation is working correctly, we're still not certain that we covered all edge cases. If you don't feel like gambling on this, it might be better to use version 4.0.3.

Fixed an issue where --ignore-public failed on references that contained multiple attributes (like public static)

• --ignore-public will now correctly avoid enums

Files containing emojis will now be correctly obfuscated. This includes types that have emojis in their names and everything else. With this release, the relevant limitation was removed from SOURCEKITISSUES.md.

SwiftShield has been completely remade. The first version was highly untested, and new features were very hard to develop and maintain. The code is now highly tested, including tests that run xcodebuild and SourceKit themselves. Now, we're able to know if SwiftShield works correctly with newer versions of Xcode, and new features are easy to test.

Functionality is mostly the same, but the usage details changed. Check the README for the newest set of instructions.

• -sdk renamed to --ignore-public
• Removed manual mode. Manual mode was created because the automatic mode was extremely unstable. Now that SourceKit works (mostly) correctly, the manual mode lost its purpose. If you were relying on it, let me know.
• Removed Storyboard Obfuscation. This feature was untested, extremely hard to maintain and had tons of untreated edge cases. Since the usage of Storyboards is almost nonexistent in large projects (the target of SwiftShield), the feature was removed. SwiftShield will now only support view code obfuscation.
• Revamped the example project.

Fixed a problem with enum elements

• Enums will be obfuscated, expect ones with the CodingKeys suffix - @hwdavr