You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2023-12-07] [HOLD for payment 2023-12-06] Wallet - On first try, SSN is verified after second attempt to submit the form #32083
Version Number: 1.4.4.0 Reproducible in staging?: y Reproducible in production?: unable to check 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:
Follow the flow until your reach the "Additional details" page.
Fill the form with following data: First name: Alberta, Last name: Bobbeth, SSN: 3333, Any other information for the rest of the fields.
Tap on "Save & continue".
Expected Result:
The user should be taken to the nest step without any issues.
Actual Result:
An error message appears the first time the user hits the "Save & continue" button. If the user taps on it again without any change on the fields, then the SSN is verified.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
changed the title [-][HOLD for payment 2023-12-06] Wallet - On first try, SSN is verified after second attempt to submit the form[/-][+][HOLD for payment 2023-12-07] [HOLD for payment 2023-12-06] Wallet - On first try, SSN is verified after second attempt to submit the form[/+]on Nov 30, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.5-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-12-07. 🎊
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
@luacmartins Apparently this failed on the latest staging #32266 (comment) maybe there is some misunderstanding with expected resutlts, but I am reopning just so we can check if this is fine.
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary (SO)[https://stackoverflowteams.com/c/expensify/questions/17778].
Activity
github-actions commentedon Nov 28, 2023
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
melvin-bot commentedon Nov 28, 2023
Triggered auto assignment to @robertjchen (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.luacmartins commentedon Nov 28, 2023
We CPed a revert. Closing.
6 remaining items
[-][HOLD for payment 2023-12-06] Wallet - On first try, SSN is verified after second attempt to submit the form[/-][+][HOLD for payment 2023-12-07] [HOLD for payment 2023-12-06] Wallet - On first try, SSN is verified after second attempt to submit the form[/+]melvin-bot commentedon Nov 30, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.5-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-12-07. 🎊
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
mountiny commentedon Dec 1, 2023
@luacmartins Apparently this failed on the latest staging #32266 (comment) maybe there is some misunderstanding with expected resutlts, but I am reopning just so we can check if this is fine.
Feel free to close again if all if expected
melvin-bot commentedon Dec 7, 2023
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary (SO)[https://stackoverflowteams.com/c/expensify/questions/17778].
luacmartins commentedon Dec 8, 2023
This is expected. Closing!