New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Swift use #1
Comments
It's unfortunate that most of the important methods aren't bridged over to Swift. I heard in XCode 7 they may get bridged over. You can use newWithSaltUnsafe(<_SALT_>) if you want but you should not UNLESS YOU KNOW WHAT YOU ARE DOING. This is because the salt needs to be dynamically created without reference to any hard-coded strings. My recommendation is listed here for Swift: https://github.com/pjebs/Obfuscator-iOS#step-1---generate-objective-c-code and then Obfuscator.reveal(CC, usingStoredSalt: "swift") |
If your AppDelegate is in Swift, you can actually create an Objective C class that implements:
That way it won't interfere with the rest of your swift code. |
Hey, the storeKey: forSalt: doesn't bridge to swift. Is the only way around this to create the Obj-C class in the AppDelegate or create another Obj-C class? |
That is correct:
|
Thanks for the quick response! ended up going with 2 |
thanks for the suggestion (#2)...helped me as well |
I am working on a Swift project and I included this lib in my podfile. |
Add to bridging header |
Hello. How can i use this with swift?
Is it generated by:
? or how?
The text was updated successfully, but these errors were encountered: