I found this odd behaviour that is probably a bug.
Here are the steps that produce it for me:
- Create a user account (I created it through client API RegisterPlayFabUser);
- Have it scheduled to be deleted through a scheduled task with "Delete Player" action;
- Login with the same credentials through client api LoginWithEmailAddress;
Expected behaviour would be to not let the user login.
Actual behaviour is a new account is created with no data through the client api login call.
The master account player is indeed deleted (not pending) and does not show up anymore in the game manager dashboard.
After the unexpected login, the new user pops up in the game manager.
In the documentation of LoginWithEmailAddress it clearly states it should not create new accounts.
If I delete the master account through the game manager dashboard, the issue does not happen.