@newatlanta19006 I’ve not had the chance to try and reproduce the use case. Are you able to reproduce the issue in local development or does it only happen on your cloud server setup?
Is it possible you can upgrade to the latest Nakama release (2.12.0) and see if it resolves your issue?
I haven’t been able to reproduce it on our development environment yet. It has the same set up as our production environment but far less load of course.
We can try upgrading Nakama but I am not confident in that solution because I dont think the rpc call is ever executing or reaching Nakama from the .NET server.
We can try upgrading Nakama but I am not confident in that solution because I dont think the rpc call is ever executing or reaching Nakama from the .NET server.
If the request doesn’t reach the server I’m not sure how I can help any further. What do you suggest?
The request doesn’t reach the Nakama server because the .NET client is nullReferencing in RpcAsync.