You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ x] I can reproduce the issue with the latest SDK release, and my server is updated to the latest version.
Issue Description
This issue is applicable in a specific scenario when there are 2 user wallets linked using Moralis.link with the parse server.
Let's say we have successfully linked wallet 2 with wallet 1. Now when we try to authenticate with wallet 1 again it it creates a duplicate user object in _user class instead of using the existing user object.
Steps + code to reproduce
This is happening when v1 sdk is used with parse server
Authenticate with user wallet 1.
Link user wallet 2 using Moralis.link function.
constunsub=Moralis.onAccountChanged(async(account)=>{constconfirmed=confirm("Link this address to your account?");const{ message }=awaitMoralis.Cloud.run("requestMessage",{address: account,chain: "0x1",networkType: "evm",});if(confirmed&&account){awaitMoralis.link(account,{signingMessage: message,});}});
Logout from the current user session linked to wallet 2.
Authenticate with user wallet 1 again.
If we check the parse dashboard now you should see two user objects for wallet 1.
Actual Outcome
Duplicate user object is created even when there is an existing user object.
Expected Outcome
Existing user object should be reused when we re-authenticate with wallet 1
Environment
Server
Moralis server version: Self-hosted server
Client
Moralis SDK version: "moralis-v1": "^1.12.0",
Operating system: not applicable
Browser: not applicable
Logs
The text was updated successfully, but these errors were encountered:
New Bug Report
Checklist
Issue Description
This issue is applicable in a specific scenario when there are 2 user wallets linked using
Moralis.link
with the parse server.Let's say we have successfully linked wallet 2 with wallet 1. Now when we try to authenticate with wallet 1 again it it creates a duplicate user object in
_user
class instead of using the existing user object.Steps + code to reproduce
This is happening when v1 sdk is used with parse server
Moralis.link
function.If we check the parse dashboard now you should see two user objects for wallet 1.
Actual Outcome
Duplicate user object is created even when there is an existing user object.
Expected Outcome
Existing user object should be reused when we re-authenticate with wallet 1
Environment
Server
Client
Logs
The text was updated successfully, but these errors were encountered: