Await _parseClient.GetCurrentUser is null after login

[chamboryk]

New Issue Checklist

• [X] I am not disclosing a vulnerability.
• [X] I am not just asking a question.
• [X] I have searched through existing issues.
• [X] I can reproduce the issue with the latest versions of Parse Server and the Parse .NET SDK.

Issue Description

After login, the current user is null Unity 2020.3.11

Steps to reproduce

    _parseClient = new ParseClient("myAppId", "http://localhost:1337/parse/", "",
        new LateInitializedMutableServiceHub { },
        new MetadataMutator
        {
            EnvironmentData = new EnvironmentData { OSVersion = SystemInfo.operatingSystem, Platform = $"Unity {Application.unityVersion} on {SystemInfo.operatingSystemFamily}", TimeZone = TimeZoneInfo.Local.StandardName },
            HostManifestData = new HostManifestData { Name = Application.productName, Identifier = Application.productName, ShortVersion = Application.version, Version = Application.version }
        },
        new AbsoluteCacheLocationMutator
        {
            CustomAbsoluteCacheFilePath = $"{Application.persistentDataPath.Replace('/', Path.DirectorySeparatorChar)}{Path.DirectorySeparatorChar}Parse.cache"
        }
    );
    Debug.Log($"{Application.persistentDataPath.Replace('/', Path.DirectorySeparatorChar)}{Path.DirectorySeparatorChar}Parse.cache");
    _parseClient.Publicize();

            var loginResult = await _parseClient.UserController.LogInAsync(SystemInfo.deviceUniqueIdentifier, SystemInfo.deviceUniqueIdentifier, new LateInitializedMutableServiceHub { }); //login result not null
            var currenSession = await _parseClient.GetCurrentSessionAsync(); //currentSession == null
            var currentUser = _parseClient.GetCurrentUser();//currentUser == null

Actual Outcome

var currentUser = _parseClient.GetCurrentUser();//currentUser == null

Expected Outcome

var currentUser = _parseClient.GetCurrentUser();//currentUser != null

Environment

Server

• Parse Server version: ^4.5.0
• Operating system: Windows 10
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Local (http://localhost:1337/parse/)

Database

• System (MongoDB or Postgres): MongoDB
• Database version: N/A
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): remote MongoDB Atlas

Client

• Parse .NET SDK version: v2.0.0-develop-1

[Kellokes]

Hi all,

Any update on this bug? What is the best way to fix or create a workaround for this? I saw that when I use this cmd _parseClient.GetCurrentUser().SessionToken; I received the Token when the Login is Successful, otherwise I get null, would checking this be a good alternative to proceed with login validation?