I heard that IOS does not need code obfuscation when building and deploying apps to the App Store. I googled out of curiosity, but there's no clear answer. I'd appreciate it if you could explain it in detail. Help me.
ios swift objective-c
As you may have already seen, https://realm.io/kr/news/conrad-kramer-reverse-engineering-ios-apps-lyft/ iOS reverse engineering, but I think this document will sort it out.
Putting code into the app - Cyclop demo (7:44)
Q: Does the device still have to be out of jail if I'm debugging my app using Cycript?
Conrad: You don't have to break out of jail if it's your app. How to include this tool in your app is available at cycript.org
It's detailed and you can link it to the demo to debug it now.
Decrypt executable - dumpecrypted demo (11:28)"
Let's take a look at the actual code when the next app is not running.
This requires a little bit of a complicated escape, but it can be done easily with a little practice.
"Because we can re-certify Divis' apps,
Apple is putting encrypted apps on the store and preventing them from being shared with others."
Compared to Android, the iPhone has a lot of freedom and many restrictions. It is impossible to redistribute using executable files like apk, so I think it is not obfuscating I'm guessing carefully, so I think there's less information about obfuscation than Android. (Simply my idea.) (Of course, if you break out of prison, the story is different.))
Of course, it's not the answer, but I think it will help to some extent.
If there is anything wrong, please feel free to tell me :D
© 2024 OneMinuteCode. All rights reserved.