Rank 5: Hypervisor
nope, nope there is no account assosiated with that email exits
Votes
0
Replies
24
Participants
Unknown
Messages
25
Rank 5: Hypervisor
nope, nope there is no account assosiated with that email exits
Rank 5: Hypervisor
what we did, is there was already accont & then deleted that account & then tried to login again & then error happened... it only happening since last 8-12 hr*
The account that was deleted has the same email?
An already existing account with the same email was deleted from Auth then we tried to re-create an account with the same email hence the error we also tried to re login
Rank 5: Hypervisor
yap the account deleted had same email
So I'm pretty sure the previous user had an identity created with the oauth email and it should be deleted after the user was deleted. Can you try calling the list identities API? Maybe with the CLI or a server SDK?
Rank 5: Hypervisor
yaa account was created via OAuth, btw just trying to call the api via CLI &ping back in few mins
Rank 5: Hypervisor
getting this as output...
{"total":0,"identities":[]}
Rank 5: Hypervisor
any update on this, as it's quite ciritical issue
Weird...I don't see why you would be getting the error then 🧐
Rank 5: Hypervisor
excatly... it only happening since last 24 hr only
Rank 5: Hypervisor
also, it's very critical issue without it getting fixed can't move ahead
Rank 5: Hypervisor
ok now not facing the issue... it's seems no longer happening just checked...
Rank 5: Hypervisor
A user with the same email already exists in the current project.
[SOLVED] A user with the same email already exists in the current project.
Is it possible it took some time for the delete to complete? Or there was something cached? Or something like that?
Yes, it may have taken some time to delete
Rank 5: Hypervisor
again it's happening... just deleted account & now right away trying to login and it's giving same error
Rank 5: Hypervisor
A user with the same email already exists in the current project.
Rank 5: Hypervisor
I guess will sleep for now... seems some issue related to caching causing this ...
Rank 5: Hypervisor
on the colonse too same...
yes the background job is a little delayed
Rank 5: Hypervisor
is it supposed to be that way or will it be fixed?
We have some improvements planned for the deletes worker
Rank 5: Hypervisor
hope it happens soon, just trying to test user related mechanisms