[Bug] The type of the cb value is being forced into string in RegisterNUICallback

[taoletsgo]

Summary

The cb value in RegisterNUICallback is not being correctly passed to js

Issue type

Client

Repro rate

Always

Server build version

b96

OS

No response

CPU

No response

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

None

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

None

Hosting provider

None

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

The reproduction code is at the end of the discussion

Expected Behavior

The cb value should remain table/object, number, or string, rather than being forced into string in all cases

Actual Behavior

The type of the cb value is being forced into string in RegisterNUICallback

Evidence

No response

Additional Context

RegisterNUICallback("test", function(data, cb)
	cb({mode = 1, label = "car name"})
end)

RegisterNUICallback("print", function(data, cb)
	print(data.cbType) -- print "string"
end)

$.post(`https://${GetParentResourceName()}/test`, JSON.stringify({}), function (cb) {
	console.log(typeof cb);
	$.post(`https://${GetParentResourceName()}/print`, JSON.stringify({cbType : typeof cb}));
});

btw console.log does not print in client console

[wolfram-cfx]

Thanks, we are looking into this.

[taoletsgo]

nvm I will deserialize cb value myself

[wolfram-cfx]

Thanks, we will keep it open until we checked it ourself.

[Gogsi]

A fix for this bug has been implemented and is available in the August 4 patch. Please try again and let us know if the issue persists. Thanks for your help!

[taoletsgo]

confirmed that this issue is fixed

[taoletsgo]

confirmed fixed in b110