Repository navigation
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.2.71-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2219752/test-runs/TR-2266/folder/13176868/41237324/1054918525?sort=%2Bidentifier
Email or phone of affected tester (no customers): sustinov@applausemail.com
Issue reported by: Applause - Internal Team
Action Performed:
- Open Expensify app
- Log in with your HT account
- Create a new WS
- Go to the More features menu in the WS settings
- Enable Taxes
- Go to the Taxes menu
- Tap +Add rate
- Tap the Name field
Expected Result:
When navigating to the Tax name editing menu, the name field should be autofocused and the keyboard should appear
Actual Result:
No autofocus in the name editing menu tax
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
- MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidence
Bug7019796_1764782332205.Screenrecording_12-03-2025_20-10-59_1.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021999623089089742669
- Upwork Job ID: 1999623089089742669
- Last Price Increase: 2026-03-09
- Automatic offers:
- samranahm | Contributor | 109838252
Activity
melvin-bot commentedon Dec 3, 2025
Triggered auto assignment to @stephanieelliott (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.samranahm commentedon Dec 3, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
No autofocus in the name editing menu taxes
What is the root cause of that problem?
We're missing the
autoFocushereApp/src/pages/workspace/taxes/WorkspaceCreateTaxPage.tsx
Lines 114 to 117 in 0134330
What changes do you think we should make in order to solve the problem?
Add
autoFocusparam toInputWrapperApp/src/pages/workspace/taxes/WorkspaceCreateTaxPage.tsx
Lines 114 to 117 in 0134330
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
Eskalifer1 commentedon Dec 4, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
Tax - No autofocus in the name editing menu taxes
What is the root cause of that problem?
We are on this page:
App/src/pages/workspace/taxes/WorkspaceCreateTaxPage.tsx
Lines 114 to 126 in e8bcafa
And here is the code of this component:
App/src/components/TextPicker/index.tsx
Lines 55 to 86 in e8bcafa
The component itself renders the input and already has logic for focusing:
App/src/components/TextPicker/TextSelectorModal.tsx
Lines 95 to 110 in e8bcafa
App/src/components/TextPicker/TextSelectorModal.tsx
Lines 164 to 172 in e8bcafa
And on all platforms except IOS native, the focus occurs.
But why doesn't this happen on iOS? I couldn't find any specific article or documentation describing this, but the problem lies in how Fullstory works on iOS. At some point, this library (or the
@fullstory/babel-plugin-annotate-reactplugin) injects its own ref. As a result, even though we destructured ref here:App/src/components/TextPicker/index.tsx
Lines 27 to 28 in e8bcafa
And there should be no ref in
rest, but at the moment when we pass this rest here:App/src/components/TextPicker/TextSelectorModal.tsx
Line 170 in e8bcafa
We have a ref from FullStory, which overwrites our custom ref and therefore fails the
inputRef.currentcheck and no focus occurs.We can tell that this is a ref from FullStory by the name of the symbol:

For comparison, AmountPicker has the same problem, but first the props are passed destructured and only then ref. Because of this, this bug does not occur there. If you change the order to the same as in
TextSelector, this bug will also occur there:App/src/components/AmountPicker/AmountSelectorModal.tsx
Lines 67 to 72 in e8bcafa
I think this is sufficient for RCA, since any deeper explanation would relate to how the library itself works, which is not relevant to this project.
What changes do you think we should make in order to solve the problem?
We need to use the same pattern that we use in other parts of the project (such as in
AmountSelectorModal), namely passingrefat the end.What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
cretadn22 commentedon Dec 4, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
Tax - No autofocus in the name editing menu taxes
What is the root cause of that problem?
we already has logic for focusing, but this logic doesn't work on IOS native
App/src/components/TextPicker/TextSelectorModal.tsx
Lines 95 to 110 in e8bcafa
What changes do you think we should make in order to solve the problem?
Passing autoFocus into this place
App/src/components/TextPicker/TextSelectorModal.tsx
Line 164 in e8bcafa
What alternative solutions did you explore? (Optional)
[-]Tax - No autofocus in the name editing menu taxes[/-][+][$250] Tax - No autofocus in the name editing menu taxes[/+]melvin-bot commentedon Dec 12, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021999623089089742669
melvin-bot commentedon Dec 12, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak (
External)246 remaining items
eVoloshchak commentedon Sep 17, 2026
Contributor+ Checklist:
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: This was a bug in a third-party package
Link to the comment on the Issue:
[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: regression wasn't critical
[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.
Regression Test Proposal
Test:
Do we agree 👍 or 👎
eVoloshchak commentedon Sep 17, 2026
@TaduJR, looks like this caused 3 regressions, is that correct?
TaduJR commentedon Sep 17, 2026
@eVoloshchak
Yes but the regression was from upstream not from us.
melvin-bot commentedon Sep 18, 2026
@mallenexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
mallenexpensify commentedon Sep 20, 2026
Claude posting on behalf of Matt:
$75 to @TaduJR (Contributor) and $75 to @eVoloshchak (Contributor+). 25% of the $250 job price, the regression floor.
Claude posting on behalf of Matt.
PAYRUBRICTEST v2TaduJR commentedon Sep 20, 2026
Not sure if the regressions cut is applicable here. Both reverts were causes by upstream design flaws. Actually this issue was complex requiring a fix from Upstream. It could have been $500 but I left it because of the reverts. $250 is fine imo wdyt @flodnv
Thanks
flodnv commentedon Sep 21, 2026
I agree with $250
mallenexpensify commentedon Sep 21, 2026
Payment Summary
Contributor: @TaduJR paid $250 via Upwork
Contributor+: @eVoloshchak due $250 via NewDot
@TaduJR can you please accept the job below? Please reply here and tag me once you have.
https://www.upwork.com/jobs/~022102132141262506132
Is @samranahm due payment? They were assigned early on. Thx
samranahm commentedon Sep 21, 2026
@mallenexpensify No, I’m not due a payment here. We decided to go with @TaduJR’s proposal after I get assigned.
Could you please delete this offer from Upwork? #76650 (comment)
mallenexpensify commentedon Sep 21, 2026
@samranahm contract closed with zero payment, I checked 'contract not needed anymore' option.
mallenexpensify commentedon Sep 26, 2026
@TaduJR paid, apologies, I think I used the wrong snippet
JmillsExpensify commentedon Sep 30, 2026
$250 approved for @eVoloshchak