Good morning Moralis,
Posting our discord thread on the request of YNikolasKS for help with a bug in the unity SDK we have found. In order to better understand the problem this is our user journey:
We have two applications - Our web front end that we are using for user management, and our Unity game where users can login with only their usernames and passwords.
When we create a user on our web front end with just a username and password, this system works fine. However, when a user binds a wallet to their account via Metamask in the web front end username and password login stops working in Unity. This does not stop username and password working on the web front end. The error that we receive in unity when this problem occurs is:
“Error: HTTP/1.1 400 Bad Request
{“code”:206,“error”:“Insufficient auth.”}.”
It seems like this issue relates to data being set in the authData column in the _User class. Whilst this is blank (it remains blank until a user wallet is bound) password login is possible in Unity. As soon as it is set (when a user binds a wallet in the front end), the above error starts to occur. From our discussion on Discord, it seems like other users are also observing this pattern.
Additionally and strangely, we can see the user login event firing in our logger on the unsuccessful Unity login attempts. We also observe that the session document is updated for the user:
INFO || 2022-09-15 07:07:28 Ran cloud function coreservices_track for user undefined with: Input: {"event":"New server login","userId":"o-216722","distinct_id":"216722","organisation":"XXXX","subdomain":"XXXX"} Result: {"status":200,"data":{"success":true,"result":true}}
We also observe the _Session document createdWith is updated with user name and password login:
{ "action": "login", "authProvider": "password" }
Despite this, it does not result in a successfully instantiated Moralis User inside Unity. This leads us to believe this is purely a problem with the Unity SDK.
On discord we saw that other people are experiencing the same problem and the advice from YNikolasKS was to try this:
“For the {“code”:206,“error”:“Insufficient auth.”} issue - There was a security update on the backend that now re-validates the signature every time it is posted. I will need to add a patch for this in the Unity SDK.
For now to get past the issue, before you calluser.SaveAsync(), clear the authData array. For example:user.authData.Clear();
await user.SaveAsync();The same will work for custom objects”
The only logical place that we could see to try calling these functions was after the unsuccessful login event inside Unity. Our theory being that the user is being partially instantiated and clearing the authData table in the _User document then trying to resave might allow the user to be fully bound. This did not appear to work, though.
If helpful, I have recorded all login events from a cloud logger during this process. Let me know and I will email them to someone.
Additional things I will try today:
Using monogsh to delete the authData column after a wallet has been bound and seeing if this fixes things in Unity without affecting the front end application.
Moralis software versions in use:
Unity:
Unity Moralis SDK release : 1.2.10
Unity version: 2021.3.0f1
Webfront end:
Moralis-v1 : 1.11.0
React-moralis : 1.4.0