And with Lua I should probably write something detailed up on how to go about testing
can you ask the question on the forums and I'll put my notes there?
Thanks @fsufyan do you think it's something I should incorporate into the next client sdk release? Make it clearer how to set the various SSL cert versions the client sdk will be allowed to accept?
@novabyte as I commented on the Github issue, I'm not just running "client.NewSocket()". I'm using the exact code in the docs. With the Connected and Closed listeners and ConnectAsync being called. There's nothing different about our Unity code, except we're using " UnityWebRequestAdapter.Instance" per your suggestion. Our token is set to expire after 8 minutes. I pull this out and put it in a test project with no other code, and I get the same results.
@novabyte I can confirm it creates the user successfully, with no errors.
Hello guys, I was looking in my leaderboard records, in database. I wondered that there were records assigned to usernames that didn't belong to anyone. For example, there was a record submitted by user X, while there is not any user named X. In my scenario, users have a default username before registration, and after registration, the username changes by the user. I think leaderboard records are not updated after updating the username, leading me to this issue, Am I right?
Now I'm almost sure that updating account doesn't update leaderboard records, I checked the records owner id, It belongs to a valid user, with a valid username Y. while still record username is X
@mohsenyz Yes leaderboard records are not retroactively updated after the user changes their username. The username field in the entry is cached and replaced only on a new score submission
As you can imagine the performance would be terrible if we retroactively updated all old leaderboard records for a user any time they update their username
08-17 12:22:54.622 30420 30436 E Unity : InvalidHttpResponseCodeException: 400 Bad Request
08-17 12:22:54.622 30420 30436 E Unity : at Nakama.Ninja.WebSockets.WebSocketClientFactory.ThrowIfInvalidResponseCode (System.String responseHeader) [0x00071] in <0b8079027a0346b2a98515fbce966890>:0
08-17 12:22:54.622 30420 30436 E Unity : at Nakama.Ninja.WebSockets.WebSocketClientFactory+<ConnectAsync>d__7.MoveNext () [0x000bd] in <0b8079027a0346b2a98515fbce966890>:0
08-17 12:22:54.622 30420 30436 E Unity : --- End of stack trace from previous location where exception was
08-17 12:22:54.622 30420 30436 E Unity : at Nakama.Ninja.WebSockets.WebSocketClientFactory.ThrowIfInvalidResponseCode (System.String responseHeader) [0x00071] in <0b8079027a0346b2a98515fbce966890>:0
08-17 12:22:54.622 30420 30436 E Unity : at Nakama.Ninja.WebSockets.WebSocketClientFactory+<ConnectAsync>d__7.MoveNext () [0x000bd] in <0b8079027a0346b2a98515fbce966890>:0
08-17 12:22:54.622 30420 30436 E Unity : --- End of stack trace from previous location where exception was
Because all responses will carry a reason, not just a generic "Bad Request"
So it was a common problem to see where the reason message was swallowed before the client presented it to you
If that's not the case then there's something else odd going on
You're going through nginx, right? Have you tried without it - hit Nakama directly?
Yes I'm on "v2.2.2". Unity Version 2019.1.6f1. The difference for the client code is that we're using "UnityWebRequestAdapter.Instance" when we create the client, as without it we run into the Unity libc issue referenced here: heroiclabs/nakama-unity#74
I'm able to create and authenticate users properly. They all show up in the DB. But I can't do anything else until I get the connection working.
What happens if you just navigate to your server address with the
/ws
You should see an error from Nakama about an invalid session token
can you confirm you get that error?
can you send me the output of
session.AuthToken field?
I'd like to decode the session token and inspect the contents
{
"exp": 1566062634,
"uid": "25811ab5-35c7-4598-8f95-e936c0e82a32",
"usn": "FrFjMQtOWY"
}
It decodes correctly and the signature verifies against the default signing key
@CamDHall What version of Unity engine do you use?
using System;
using System.Threading.Tasks;
using Nakama;
using UnityEngine;
public class Example : MonoBehaviour
{
private IClient _client;
private ISocket _socket;
private async void Awake()
{
_client = new Client("defaultkey", UnityWebRequestAdapter.Instance);
_socket = _client.NewSocket();
_socket.Closed += () => Debug.Log("Socket closed.");
_socket.Connected += () => Debug.Log("Socket connected.");
_socket.ReceivedError += e => Debug.LogErrorFormat("Socket error: {0}", e.Message);
var deviceId = SystemInfo.deviceUniqueIdentifier;
var session = await _client.AuthenticateDeviceAsync(deviceId);
await _socket.ConnectAsync(session);
Debug.Log("After socket connected.");
}
private void OnApplicationQuit() => _socket?.CloseAsync();
}
I get no errors at all
I ran it with our docker-compose file using the latest Nakama 2.6.0 release of the server