-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Wallet - Error appears when system attempts to verify Onfido information #31237
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
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @bondydaa ( |
The issue was not posted on Upwork, but I still tried replicating this. I did my ID verification on my iOS web browser while the staging app was running on my machine. There was no way for the error to be shown on Onfido page in my mobile as it says me to check the status on the desktop app. I initially was seeing the If the message was shown while the verification was happening in the background, then the issue could be in this logic here . We need to modify the condition |
📣 @anuraagdjain! 📣
|
@kbecciv looks like we had some big incident this weekend around the time you created this, can you test again now and see if you still have issues? |
@bondydaa The issue is still being reproduced |
@marcaaron @nkuoch @MariaHCD since ya'll were involved with https://github.com/Expensify/Web-Expensify/pull/39342, any ideas here? @kbecciv what email/login is this from so we can look up logs? |
That error is expected if the Onfido verification failed. Once we have the email that was used for testing, we can confirm whether the Onfido check failed (and why) |
ran the query that looks up the wallet for a user.
I can't see the original images/video on the OP but from the looks of it there is an error while trying to do the validation checks? |
I tested this myself on a test account and it seemed to work. Looking for requests for looks like there are some for which have these logs:
which mostly looks like it worked and looking up that bankaccountid it does have the correct info
Seems like something broke before we could call onfido for |
oh but those are all from the 10th. |
went back to the thread to confirm a question i had |
I'm going to remove the deploy blocker from this, since I tested on staging and couldn't reproduce it might be something specific to the applause testing account but we don't need to block on it I don't think. |
For For In this case, this account will not be able to continue with the wallet KYC process. This is expected behavior for now, we have some ideas of allowing a user to retry Onfido at least once but that is not in place just yet. So I think we're good to close this one out. Thoughts, @bondydaa? |
👍 yep agreed |
Uh oh!
There was an error while loading. Please reload this page.
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.3.98.0
Reproducible in staging?: y
Reproducible in production?: can not test on production
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR #30791
Action Performed:
Pre-requisite: user must be logged in.
Expected Result:
The system should approve or reject the information provided on Onfido page.
Actual Result:
Error appears when system attempts to verify Onfido information
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: