-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix for SDK stuck in bad state when email or phone number fails API validation #127
Conversation
Makes sense to me. I do wonder if we should do anything more than just drop it out of the queue, like emit a warning or error message. I know last spring we did discuss whether to include any kind of phone or email validation and decided to leave that up to the server at the time. |
Documenting for viz - We discussed this internally and decided to silently fail for now mainly due to not have targeted error codes from the API. We do at some point expect to retry based on more accurate error codes from the API. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, were you going to merge in the deque/dequeue branch into this one also?
Yup, was just going to address Noah comments and then go for the merge. Doing it now. |
Description
We had a customer open a issue where they pointed out that the app is stuck in a bad state whenever the email or phone number fails validation. This code aims to do two things -
We try to keep the SDK fairly light weight and dequeue the request vs. trying again.
Check List
Manual Test Plan
Case 1: Invalid phone number
Case 2: Invalid email
Same as above except using a invalid email instead of a phone number.