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 2024-11-13] [$250] iOS - Search - Search input field does not auto focus #51482
Version Number: 9.0.54-0 Reproducible in staging?: Y Reproducible in production?: N If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Email or phone of affected tester (no customers):applausetester+kh1610015@applause.expensifail.com Issue reported by: Applause - Internal Team
Action Performed:
Launch ND app or hybrid
Tap on the search icon on the top right
Expected Result:
Search input field will auto focus (production behavior)
Actual Result:
Search input field does not auto focus
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Android: Standalone
Android: HybridApp
Android: mWeb Chrome
iOS: Standalone
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceBug6645639_1729867786972.ScreenRecording_10-25-2024_22-47-54_1.mp4
👋 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 [-][$250] iOS - Search - Search input field does not auto focus[/-][+][HOLD for payment 2024-11-13] [$250] iOS - Search - Search input field does not auto focus[/+]on Nov 6, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.57-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@suneox@twisterdotcom The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other:
Where bug was reported:
2a. Reported on production
2b. Reported on staging (deploy blocker)
2c. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: I think there isn’t an offending PR here, as this is related to an infrastructure update included in this PR.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again. N/A: this issue only happen on specific platform and auto focus doesn't break functionality
Activity
melvin-bot commentedon Oct 25, 2024
Triggered auto assignment to @yuwenmemon (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 25, 2024
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 25, 2024
👋 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:
lanitochka17 commentedon Oct 25, 2024
Production:
RPReplay_Final1729868136.1.MP4
Beamanator commentedon Oct 28, 2024
There seem to be multiple auto-focus bugs right now 🤔
ChavdaSachin commentedon Oct 28, 2024
And they are specific to IOS.
Beamanator commentedon Oct 28, 2024
@yuwenmemon since this is iOS-specific & related to focuses, I had a theory here what the cause could be - but maybe we could downgrade this to NAB?
yuwenmemon commentedon Oct 28, 2024
Same root cause as: #51464
Beamanator commentedon Oct 29, 2024
Agreed in slack this isn't a bad enough bug to block deploy
22 remaining items
[-][$250] iOS - Search - Search input field does not auto focus[/-][+][HOLD for payment 2024-11-13] [$250] iOS - Search - Search input field does not auto focus[/+]melvin-bot commentedon Nov 6, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Nov 6, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.57-10 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 2024-11-13. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Nov 6, 2024
@suneox @twisterdotcom The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
suneox commentedon Nov 12, 2024
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: I think there isn’t an offending PR here, as this is related to an infrastructure update included in this PR.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again. N/A: this issue only happen on specific platform and auto focus doesn't break functionality
twisterdotcom commentedon Nov 13, 2024
Payment Summary: