Last night we saw a smattering of errors when somebody tried to sign up. The underlying issue wasn't that they already had a Sierra account (which we already handle correctly); it's that they had two. This should be impossible – we cleaned up all the duplicate accounts before launching the new user sign-in, and Auth0 should prevent this from happening – but it did, and we give a less than helpful error:
This patch adds a DuplicateUsers response status from the getRecordByEmail() method on the Sierra client, and then we can respond to it with a more actionable error message:
This copy is based on a similar error which already works correctly on the sign-in screen:
I don't know why one error is in a red box and one is in inline text and I'm not going to spend the time to work it out; this should help the handful of users who are affected by this issue – and possibly prompt LE&E to work out where this is coming from.
Last night we saw a smattering of errors when somebody tried to sign up. The underlying issue wasn't that they already had a Sierra account (which we already handle correctly); it's that they had two. This should be impossible – we cleaned up all the duplicate accounts before launching the new user sign-in, and Auth0 should prevent this from happening – but it did, and we give a less than helpful error:
This patch adds a
DuplicateUsersresponse status from thegetRecordByEmail()method on the Sierra client, and then we can respond to it with a more actionable error message:This copy is based on a similar error which already works correctly on the sign-in screen:
I don't know why one error is in a red box and one is in inline text and I'm not going to spend the time to work it out; this should help the handful of users who are affected by this issue – and possibly prompt LE&E to work out where this is coming from.