Ambiera ForumDiscussions, Help and Support. |
|
|
|||||
|
When parsing the following code: var xml:XML = <root><data param="value"/></root>; that always corrupts the xml string due to the parser does not realize that is a xml data instead of a normal string. another issue is that syntax: var xml:XML = new XML(...); trace(xml.@value) The value will be obfuscated unexpectedly. the "value" is actually xml.attributes["value"] please kindly correct aboves. thanks. |
||||
|
Ah, that's not nice. You could add 'value' as symbol to ignore, and turn of string encryption as workaround for now. Thanks for posting. |
||||
|
i have the same problem, and adding every value as symbol to ignore is not very pleasant, because we have a very big project. when will you release a fix for this bug? just bought 2 licences for our company greetings manifreaky
turns to:
|
||||
|
irrfuscator 1.3.2 supports E4X attributes, try it out, hope it helps: http://www.ambiera.com/irrfuscat... |
||||
|
Hi, thanks for your fast update, the parameters are okay now. but there ist another problem with e4x: the "label" in the e4x expression should not be obfuscated into _wj564, looks like he searches and replaces without checking if it is an e4x identifier
turns to:
|
||||
|
Yes, this is a problem you'd have to solve with the ignore list, unfortunately. The reason is the following: irrfuscator is not a compiler but more a 'guesser'. (it actually cannot compile your code because it needs to be able to obfuscate your code even if it is not compilable, like for example before running a preprocessor). So it doesn't know that XML is a dynamic class and that 'label' is a dynamic symbol. You simply need to put that into the ignore list to make this work, I'm sorry. Some few more details are written down in the FAQ. An alternative would be to use the xmlnode["foobar"] syntax. Or you could try to use the binary .swf obfuscator, alternatively. |
|