You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would recommend adding built-in types to the RESERVED_NAMES constant in NameMapper, such that jadx will rename identifiers comprised of these strings. They are not valid user-assigned identifiers (due to the name collision), and are attractive obfuscation remaps due to the issues that they can cause. Note that jadx-gui rename action in editor does not work for identifiers that collide with built-in type names (the right-click rename in folder view must be used.)
Sharing my recommended list in "Relevant log output or stacktrace field" of this form.
It looks like this has been mistagged as Bug (something like Enhancement would be more appropriate.) Apologies, I am having trouble fixing the tag when I try to edit the issue.
Issue details
I would recommend adding built-in types to the RESERVED_NAMES constant in NameMapper, such that jadx will rename identifiers comprised of these strings. They are not valid user-assigned identifiers (due to the name collision), and are attractive obfuscation remaps due to the issues that they can cause. Note that jadx-gui rename action in editor does not work for identifiers that collide with built-in type names (the right-click rename in folder view must be used.)
Sharing my recommended list in "Relevant log output or stacktrace field" of this form.
Relevant log output or stacktrace
Provide sample and class/method full name
N/A
Jadx version
Clone of master
The text was updated successfully, but these errors were encountered: