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-12] Android - Room - Hard to focus the name input field after the error message appears #32402
Version Number: v1.4.7-0 Reproducible in staging?: y Reproducible in production?: n 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.
Thank you for handling! We should figure out why I was assigned an hourly on a weekend though - or was it just that everyone was off so it picked randomly?
changed the title [-]Android - Room - Hard to focus the name input field after the error message appears[/-][+][HOLD for payment 2023-12-12] Android - Room - Hard to focus the name input field after the error message appears[/+]on Dec 5, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.7-4 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-12. 🎊
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.
hmm that issue was resolved when I reverted #30996. Not sure why it's not reproducible. In that case, I'd just add a test step covering the issue so we make sure to test it and that's indeed fixed.
Activity
github-actions commentedon Dec 2, 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 Dec 2, 2023
Triggered auto assignment to @dangrous (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.kbecciv commentedon Dec 2, 2023
Not reproduced on production
Screen_Recording_20231202_200933_New.Expensify.mp4
luacmartins commentedon Dec 4, 2023
Potentially caused by #30996
luacmartins commentedon Dec 4, 2023
Gonna see if the revert fixes this issue
luacmartins commentedon Dec 4, 2023
Fixed on this revert #32440
dangrous commentedon Dec 5, 2023
Thank you for handling! We should figure out why I was assigned an hourly on a weekend though - or was it just that everyone was off so it picked randomly?
[-]Android - Room - Hard to focus the name input field after the error message appears[/-][+][HOLD for payment 2023-12-12] Android - Room - Hard to focus the name input field after the error message appears[/+]melvin-bot commentedon Dec 5, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.7-4 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-12. 🎊
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.
kowczarz commentedon Dec 5, 2023
I've tried to reproduce this issue on here #32432 (the #32440 is reverted, so the bug should occur) and I couldn't do it
Screen.Recording.2023-12-05.at.09.52.15.mov
luacmartins commentedon Dec 5, 2023
hmm that issue was resolved when I reverted #30996. Not sure why it's not reproducible. In that case, I'd just add a test step covering the issue so we make sure to test it and that's indeed fixed.
kowczarz commentedon Dec 7, 2023
I know, but I tested it on a branch where I reverted that revert. I just added this flow to test scenarios in #32432
luacmartins commentedon Dec 7, 2023
Sounds good! Thanks for adding that!