: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means waiting times in the issue tracker are very long and mostly depend on community. Sorry for the inconvenience.
State: invalid 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.
Hey, please take a look blahblah xD Sorry, I'll try to b shorter in my next bug reports.
If you'll use Rename invalid identifiers on the attached SWF you'll see only 1 name was
renamed, but 2 others (obfuscated) are still there.
"xXZBr71kl+L2gPa6" is invalid identifier, it gets renamed.
What other invalid identifiers are there in the file?
Other class names - "h0UmrKoAY2kCS2v9" and "Qr1gn7zHfwYVVISs" are valid AS identifiers.
They contain only letters or numbers and don't begin with number.
Yeah, you're right, both rest names are valid but still obfuscated... We talked about such
cases in terms of rename all feature request - rename invalid identifiers leaves such
valid but obfuscated fields untouched, this is not an issue if rename all will be