You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an RPC request is submitted via the C++ SDK the received reply is supposed to have payload, id and httpKey fields. Only the payload seems to contain what it should, the other two are empty. The RPC call itself is executed successfully and the reply payload is correct.
@jan-ekholm Thanks for the report! This data is not missing, it's just not expected as part of an RPC response. Client SDKs just use the same Rpc entity for both requests and responses for convenience.
We'll look into changing this if it creates confusion, but this is not currently a server bug. 👍
When an RPC request is submitted via the C++ SDK the received reply is supposed to have
payload
,id
andhttpKey
fields. Only thepayload
seems to contain what it should, the other two are empty. The RPC call itself is executed successfully and the reply payload is correct.See more complete description here: https://forum.heroiclabs.com/t/c-rpc-callback-contains-no-id/1939
The text was updated successfully, but these errors were encountered: