-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Issue with apps written on Kotlin. #529
Comments
I assume you are referring to the way the String fields are initialized:
|
Classes not inlined and things like @metadata' above the class name. |
The @metadata structure is by design not readable for humans, ist is generated by the Kotlin compiler and is used for reflection: |
This is the link can you please refer this link. obfuscation eliminated that. so there might be some workaround to achieve this in jadx decompiler Right? |
@skylot thanks for your advice. Yes, you got the point of what I want. |
@redmi111 ok. But I don't think it will be implemented soon because for general class inlining jadx need to collect usage information for such classes by scanning all code before decompilation. This is not implemented now and it will highly increase decompilation time or memory usage. For remove metadata annotation jadx need check that there is no reflection usage, this is also hard. |
Thank you for your reply. No problem. |
Anonymous class inlining implemented. @metadata annotation still not removed and don't it is really needed. |
As on the image above decompiled java bytecode of apps written on kotlin doesn't look so good. Hope there'll be a solution for this.
https://brompwnie.github.io/reversing/2018/02/12/Kotlin-and-Java-How-Hackers-See-Your-Code.html In this link I got some information that the obfuscated kotlin apps doesn't give many junks (like @metadata before class starts) as compared to non obfuscated apk. Take a look at it, Thanks.
The text was updated successfully, but these errors were encountered: