Error when tracing an unicode character (codepoints > 0xFFFF)

[ylazy]

Hi!

Please view this issue.

trace(String.fromCharCode(0x1F60A));

I thought it's a vscode issue but if it's ok with other languages then it could be an as3mxml extension issue or a compiler/runtime issue?
I don't understand how as3mxml connecting trace statements to the vscode's debug console so I cannot determine where the problem is.

Please help!

Thank you!

[joshtynjala]

The relevant code in vscode-swf-debug is here:

https://github.com/BowlerHatLLC/vscode-swf-debug/blob/c5455c0/swf-debug-adapter/src/main/java/com/as3mxml/vscode/SWFDebugSession.java#L285-L299

[joshtynjala]

I spent a little time debugging.

I confirmed that I can successfully display unicode characters in the debug console, if I hard-code them in the Java code.

The value of traceEvent.information appears to be wrong, so it seems to be a bug in the royale-compiler debugger module (or possibly in the Flash/AIR runtime). I'm not sure how to resolve.

[joshtynjala]

I've determined that when the Java debugger code reads the bytes received from AIR, it seems to be getting 0xF60A instead of 0x1F60A. It appears that something in AIR is truncating the upper bytes.

Then, I discovered this:

trace(String.fromCharCode(0x1F60A).charCodeAt(0).toString(16)); // f60a

[ylazy]

trace(String.fromCharCode(0x1F60A).charCodeAt(0).toString(16), String.fromCharCode(0x1F60A).length);

AIR 32.0.0.116 output: f60a 1
AIR 51.1.3.7 output: d83d 2

In AIR 50.2.4.5+:

AIR-7035: String.fromCharCode() should support all unicode code points

and we have to wait for AIR 52 to use codePointAt instead of charCodeAt

[ylazy]

But I guess String.fromCharCode and string.charCodeAt are not related to this issue. You can try this:

trace("😊".length);

output 2 for both AIR 32 and AIR 51

[ylazy]

More test:

AIR 32:

X.File.fromString("😊", X.File.applicationDirectory.resolvePath("testUTF16.air32.txt"));

AIR 51:

X.File.fromString("😊", X.File.applicationDirectory.resolvePath("testUTF16.air51.txt"));

Comparing the output file, I can see the same character.

So I think the compiler has been encoded the character correctly.

[ylazy]

Hi @joshtynjala I finally found out an useful info.

Using Adobe Scout I got this trace output for trace("😊"); (the last line)

Copying the last line to VSCode:

I saw the original smiley:

This means the trace function has successfully push out the smiley character. So I think the Air side is fine.