Cloud Script log.debug() not showing data?

Question

question

bodin asked Apr 17, '19

Cloud Script log.debug() not showing data?

Hi,

I'm learning how to use Cloud Script. my problem is I cannot output argument to log.debug

from this 2 lines of script:

return { input: args.inputValue };
log.debug("helloWorld:", { input: args.inputValue });

and I used game manager to run script with this argument

{"inputValue":3}

I got this return result

"FunctionResult":{"input": 3},
"Logs": [
        {
            "Level": "Debug",
            "Message": "helloWorld:",
            "Data": [
                [
                    []
                ]
            ]
        }

I don't understand why "inputValue" can be appeared in return message, but not in log.debug?

Doesn't it should be appeared in value for "Data" key?

Best regards,

Bodin

CloudScript

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 1 · 2019-04-18T01:10:45Z

bodin answered Apr 18, '19

ok, I got it now.

the "Data" part will show when I check it from Playsteam event.

2

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Seth Du ♦ commented · Apr 18, 2019 at 06:14 AM

Actually they should also show at the callback result. I have tested the log.debug just now and it works fine.

0 ·

snipaste-2019-04-18-14-07-46.png (91.7 KiB)

bodin Seth Du ♦ commented · Apr 18, 2019 at 06:23 AM

Hi @SethDu,

Thank you for helping me checking this.

I tested again, Key "Data" still not show up in Log part.

0 ·

capture.jpg (70.1 KiB)

Answer 2 · 2019-04-18T06:27:48Z

bodin answered Apr 18, '19

but if I view a raw JSON from Playstream, it's shows up normally.

capture.jpg (62.6 KiB)

2

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Seth Du ♦ commented · Apr 18, 2019 at 07:00 AM

I did more tests and I believe there is a display issue on the CloudScript tab of Player page. This occurs when the data value field is a JSON object like:

log.debug("helloWorld:", { input: args.inputValue });

or

log.debug("helloWorld:", { "testkey": "testvalue" });

if you input a string or stringified JSON object, there won't be any issue.

log.debug("helloWorld:", "{\"testkey\":\"testvalue\"}");

I will inform our team to investigate this display issue.

1 ·

bodin Seth Du ♦ commented · Apr 18, 2019 at 09:53 AM

noted & thank you very much.
It would be nice if this issue can be fixed.

1 ·

question