+ update 2020: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means we will NOT develop new features and/or fix most of bugs. We left the tracker running in case somebody from community would like to work on it. Sorry for the inconvenience.
State: new new: Initial state. As long as issue is in this state, the work on the issue has not yet begun. opened: Opened state means developer started working on the issue. Feature/Fix will probably be in the next release. postponed: This means developer is not working on it now, for some reason it cannot be implemented now. Issue may be opened again in the future. upgraded: Issue is in upgraded state when developer made changes to the program and new version was released. closed: This means the user is satisfied with issue results and no more changes are needed. invalid: These issues cannot be solved. ignored: Developer decided to take no action on this issue. returned: Program changes were made but user is not satisfied and returned the issue.
When it is off and you are trying to open an obfuscated file it fires a pile of errors.
Perhaps it's better to make some dialog to inform user and ask to turn deobfuscation on or
reject the file.
The latest version shows this tip in the source code window:
* Decompilation error
* Code may be obfuscated
* Tip: You can try enabling "Automatic deobfucation" in Settings
* Error type: EmptyStackException
Is this enough?