During tests and development sessions, it may happen that a user is authentified in the onboarding process (after filling his password), but does not exists anymore in DB (after a manual removal). In this precise situation, it is not possible anymore to save user's password during the password step.
To avoid that, we decided to throw an error, as this state is not exepcted in a production environment, and could trigger other unexpected error during the onboarding process.
CPatchane
commented
7 years ago
During tests and development sessions, it may happen that a user is authentified in the onboarding process (after filling his password), but does not exists anymore in DB (after a manual removal). In this precise situation, it is not possible anymore to save user's password during the password step.
To avoid that, we decided to throw an error, as this state is not exepcted in a production environment, and could trigger other unexpected error during the onboarding process.