Skip to content

fix: Tax - No autofocus in the name editing menu taxes#95917

Merged
flodnv merged 5 commits into
Expensify:mainfrom
TaduJR:fix-Tax-No-autofocus-in-the-name-editing-menu-taxes
Jul 21, 2026
Merged

fix: Tax - No autofocus in the name editing menu taxes#95917
flodnv merged 5 commits into
Expensify:mainfrom
TaduJR:fix-Tax-No-autofocus-in-the-name-editing-menu-taxes

Conversation

@TaduJR

@TaduJR TaduJR commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

This PR fixes the iOS-only autofocus failure on the tax name editing page by upgrading the FullStory packages to versions that no longer rewrite React refs:

  • @fullstory/react-native ^1.9.0^1.10.1
  • @fullstory/babel-plugin-react-native ^1.5.2^1.7.0
  • @fullstory/babel-plugin-annotate-react ^2.3.2^2.4.0 (required by the SDK, behavior unchanged — its new reactCompiler option is opt-in and not enabled)
  • Rebases our local FullStory.mm HybridApp crash patch from 1.9.0 to 1.10.1 (upstream file is unchanged between the two versions, so this is a rename only)

Root cause recap: On iOS New Architecture with React 19, @fullstory/babel-plugin-react-native ≤1.6.0 injected a phantom enumerable ref (sharedRefWrapper) into the props of every element annotated with FullStory attributes. That phantom ref leaked through the {...rest} spread in TextSelectorModal and overwrote inputCallbackRef on InputWrapper, so inputRef.current stayed null and the useFocusEffect focus logic silently bailed — no autofocus, iOS native only.

FullStory 1.7.0 (fullstorydev/fullstory-babel-plugin-react-native#72, stacked with fullstorydev/fullstory-react-native#151 — written by the FullStory maintainer, citing fullstorydev/fullstory-babel-plugin-react-native#64 as motivation) removes ref rewriting entirely. The plugin no longer modifies react/cjs/*.js or touches element props/refs at all. Instead, it injects a commit-phase hook into the Fabric renderer (commitMutationEffectsOnFiber in ReactFabric-{dev,prod,profiling}.js) that collects host fibers carrying FS attributes from memoizedProps and, once the shadow tree is committed to native, forwards them to the SDK via a single batched native command. Since element props are never mutated, both prior failure modes (enumerable phantom refs leaking through spreads, and non-enumerable refs being dropped by spreads) are eliminated by construction there is no ref manipulation left to regress.

Fixed Issues

$ #76650
PROPOSAL: #76650 (comment)

Tests

Test 1 — Tax name field focuses automatically:

  1. Log in and create a new workspace
  2. Open the workspace settings and go to More features
  3. Turn on Taxes
  4. Open the Taxes menu
  5. Tap + Add rate
  6. Tap the Name field
  7. Check that the cursor is already in the name field and the keyboard opens on its own — you should be able to type right away without tapping the field again
  8. Go back and tap the Value field — check the same thing: cursor ready, keyboard open

Test 2 — Emoji picker opens:

  1. Go to Account settings > Profile > Status
  2. Tap the emoji selector — check that the emoji picker opens
  3. Now open any chat and tap the emoji (smiley) icon next to the message box — check that the emoji picker opens there too

Test 3 — "New messages" badge scrolls the chat:

  1. As User A, open a chat with User B that has 15+ messages and no unread messages
  2. Scroll up to the top of the conversation
  3. As User B (on a second device), send a new message
  4. As User A, tap the New messages badge that appears
  5. Check that the chat jumps down to the new message at the bottom

Test 4 — Reordering stops on a distance expense:

  1. Log in with an account that belongs to a workspace
  2. Tap the green + button > Track distance > Map
  3. Tap Start and enter an address, then enter a Finish address
  4. Tap Add stop and enter a third address
  5. Press and hold any of the stops, then drag it to a different position in the list
  6. Check that the stop moves while you drag it and stays in its new position when you let go

Test 5 — Chat scrolls down after submitting an expense:

  1. As User A, start a chat with User B and send several messages
  2. Submit an expense to User B
  3. As User B (on a second device), pay that expense
  4. As User A, make sure there are no unread messages, then scroll up to the top of the chat
  5. Submit one more expense
  6. Check that the chat automatically jumps down to the new expense you just submitted

Test 6 — App recordings still work (FullStory):

  1. Open the app, log in, and browse around for a minute or two (open a few chats, settings pages, etc.), then close the app
  2. Check that the app opened normally at the start — no crash on launch
  3. Ask the team member with FullStory access to confirm the session shows up in FullStory and plays back normally (this part needs a FullStory account, so QA can skip it if they don't have access)
  • Verify that no errors appear in the JS console

Offline tests

Same as tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."
Same as tests

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Screen.Recording.2026-05-23.at.12.24.33.AM.mov
Android: mWeb Chrome
Screen.Recording.2026-05-23.at.12.28.46.AM.mov
iOS: Native
Screen.Recording.2026-05-23.at.12.11.24.AM.mov
iOS: mWeb Safari
Screen.Recording.2026-05-23.at.12.18.41.AM.mov
MacOS: Chrome / Safari
Screen.Recording.2026-05-23.at.12.16.45.AM.mov

@TaduJR
TaduJR requested a review from a team as a code owner July 12, 2026 18:14
@melvin-bot
melvin-bot Bot requested review from eVoloshchak and removed request for a team July 12, 2026 18:14
@melvin-bot

melvin-bot Bot commented Jul 12, 2026

Copy link
Copy Markdown

@eVoloshchak Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@github-actions

Copy link
Copy Markdown
Contributor

⚠️ This PR is possibly changing native code and/or updating libraries, it may cause problems with HybridApp. Please check if any patch updates are required in the HybridApp repo and run an AdHoc build to verify that HybridApp will not break. Ask Contributor Plus for help if you are not sure how to handle this. ⚠️

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 119bc2d926

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread package.json
@TaduJR

TaduJR commented Jul 12, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@codecov

codecov Bot commented Jul 12, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
see 9 files with indirect coverage changes

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Another round soon, please!

Reviewed commit: 2fc42ccd42

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@TaduJR

TaduJR commented Jul 12, 2026

Copy link
Copy Markdown
Contributor Author

Hi @eVoloshchak

Could you test it on a real device when you have a moment?

Thanks!

@eVoloshchak

eVoloshchak commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

@TaduJR, could you merge the latest main please?

…autofocus-in-the-name-editing-menu-taxes

# Conflicts:
#	ios/Podfile.lock
#	package-lock.json
#	package.json
@TaduJR

TaduJR commented Jul 16, 2026

Copy link
Copy Markdown
Contributor Author

@TaduJR, could you merge the latest main please?

Done @eVoloshchak

@eVoloshchak

eVoloshchak commented Jul 19, 2026

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
screen-20260719-155753-1784469455387.mp4
Android: mWeb Chrome
Screen.Recording.2026-07-19.at.16.04.47.mov
iOS: HybridApp
Screen.Recording.2026-07-19.at.15.56.46.mov
iOS: mWeb Safari
Screen.Recording.2026-07-19.at.16.03.25.mov
MacOS: Chrome / Safari
Screen.Recording.2026-07-19.at.16.05.15.mov

@eVoloshchak

Copy link
Copy Markdown
Contributor

Could you test it on a real device when you have a moment?

Build fails on a real device (not related to this PR, same behavior is on main, probably xCode version mismatch)
Tested this on a simulator, works perfectly, the issue is resolved

@melvin-bot
melvin-bot Bot requested a review from flodnv July 19, 2026 14:16
@TaduJR

TaduJR commented Jul 19, 2026

Copy link
Copy Markdown
Contributor Author

@flodnv

Would it be possible to request adhoc and test on real device from the QA team?

@github-actions

Copy link
Copy Markdown
Contributor

🚧 flodnv has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions

This comment has been minimized.

@flodnv

flodnv commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

I requested an adhoc build test on real devices.

@m-natarajan

Copy link
Copy Markdown

Passed, Web-Chrome, iPhone 13/iOS 26.5 / v9.4.35-1 PR:95917 (Pending validation in Android). Test6: couldn't validate on full story as unable to find the email logged in on my device, due to this KI

REC-20260720164027.mp4
Test.6.mp4
Test.5.mp4
Test.4.mp4
Test.3.mp4
Test.2.mp4
Test.1.mp4

flodnv
flodnv previously approved these changes Jul 21, 2026
@flodnv

flodnv commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Conflicts

…autofocus-in-the-name-editing-menu-taxes

# Conflicts:
#	ios/Podfile.lock
@TaduJR

TaduJR commented Jul 21, 2026

Copy link
Copy Markdown
Contributor Author

Conflicts

Done @flodnv

@TaduJR
TaduJR requested a review from flodnv July 21, 2026 09:25
@flodnv
flodnv merged commit c67baa1 into Expensify:main Jul 21, 2026
69 of 86 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🚧 flodnv has triggered a test Expensify/App build. You can view the workflow run here.

@melvin-bot melvin-bot Bot added the Emergency label Jul 21, 2026
@melvin-bot

melvin-bot Bot commented Jul 21, 2026

Copy link
Copy Markdown

@flodnv looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@flodnv flodnv removed the Emergency label Jul 21, 2026
@flodnv

flodnv commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Tests passed.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/flodnv in version: 9.4.42-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants