First launch per steam account fails to connect to EOS service (always). about eos_plugin_for_unity HOT 4 CLOSED

Hey, I apologize for creating another issue

Nothing to apologize for @nitrocss.

Helps us make the plugin better and better - plus I usually learn something along the way 😄

I'll look into this and the other issue first thing at the start of next week.

from eos_plugin_for_unity.

We came across this issue too.
If you look at the managing user flow from the epic documentation (https://dev.epicgames.com/docs/game-services/eos-connect-interface#managing-users) you'll see that if the user does not exist, the login API returns a EOS_InvalidUser result along with a EOS_ContinuanceToken. The token provides details about the login attempt and is required during the next steps in the login flow.

So in the flow chart provided at the above link its the red circled state that is missing from this plug-in:

We fixed this by adding a call to EOSManager.Instance.CreateConnectUserWithContinuanceToken in our ConnectLoginCallback.

For Example:

if (connectLoginCallbackInfo.ResultCode == Result.InvalidUser)
{
    //Invalid user so create one with the connect ContinuanceToken
    EOSManager.Instance.CreateConnectUserWithContinuanceToken(connectLoginCallbackInfo.ContinuanceToken, createUserCallbackInfo => { 
            Debug.Log($"CreateConnectUser.  [{createUserCallbackInfo.ResultCode}]");
        }
    });
}else{
    Debug.LogError($"Connect Login Failed.  [{connectLoginCallbackInfo.ResultCode}]");
}

The strange thing was some of our users were able to play and get a valid connect login without this logic so not sure what the difference is to cause it for only some, I've asked epic via support ticket and will update here if I hear back at all.

from eos_plugin_for_unity.

@Kenny5 Excellent to know! Thank you for this. I will add it to our tasks for the week to plug this gap. I appreciate you sharing your solution! :)

from eos_plugin_for_unity.

@nitrocss I'm going to close this issue and mark it as pending, which is how we track issues for which a work-around has been provided and a change has been introduced to the development branch, but has not yet made it into stable or filtered into our releases. Thanks again to @Kenny5 for providing such a clear overview of the problem and how to resolve it.

from eos_plugin_for_unity.