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
Wallet - SSN field is not filled after user hits back button #32085
Version Number: 1.4.4.0 Reproducible in staging?: y Reproducible in production?: cannot 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:
👋 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.
This doesn't need to be a blocker, and it looks like this could also be happening on the PROD. Also, the issue seems to have existed for quite some time now.
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 @techievivek (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.techievivek commentedon Nov 28, 2023
Even the DOB field is not filled once I go back to the form page.
techievivek commentedon Nov 28, 2023
It looks like this is happening because we don't have the
shouldSaveDraftenabled on the ssn input field.techievivek commentedon Nov 28, 2023
This doesn't need to be a blocker, and it looks like this could also be happening on the PROD. Also, the issue seems to have existed for quite some time now.
luacmartins commentedon Nov 28, 2023
I think that's intentional for security reasons.
techievivek commentedon Nov 28, 2023
Interesting, thanks for the context. Closing it.