PATCH: Android - Fix caret resetting to the beginning of the input

[ikevin127]

Explanation of Change

We're applying a patch which includes two react-native fixes (1) and (2) which were merged but will take some time to reach production. The patch is fixing an issue based in the Android native code which caused the selection caret to be reset to the beginning of the input instead at the end when the input is not empty. More details in the issue / proposal.

Fixed Issues

$ #52029
$ #50055
PROPOSAL: #52029 (comment)

Tests

Note

This PR fix only applies to Android: Native, none of the other platforms will be affected or work differently.

Precondition: Make sure to perform a clean install of node_modules and ensure the new patch is applied.

Steps for issue #52029:

1. Launch Android: Native app.
2. Login with account with expensify card enabled with bank account added, and few members invited in workspace.
3. Go to workspace settings.
4. Tap expensify card.
5. Tap issue card.
6. Select a user -> physical card -> monthly.
7. Input an amount in the Set a limit amount page.
8. Go to confirmation page.
9. Navigate back to the Set a limit amount page.
10. Verify that the cursor caret is at the end of amount, not at the begginning right after the currency symbol.

Steps for issue #50055:

1. Launch Android: Native app.
2. Log in with new account.
3. Go to Settings -> New workspace - More features - enable invoice.
4. Navigate to LHN.
5. Tap FAB -> Send invoice.
6. Enter an amount and tap Next.
7. Select a user.
8. Tap Next.
9. Enter company name and address.
10. Tap Send invoice.
11. Open invoice -> tap on Amount field.
12. Reopen the Amount field (repeat step 11).
13. Verify that the cursor caret is at the end of the amount, not at the begginning right after the currency symbol.

• Verify that no errors appear in the JS console

Offline tests

N/A.

QA Steps

Note

This PR fix only applies to Android: Native, none of the other platforms will be affected or work differently.

Steps for issue #52029:

1. Launch Android: Native app.
2. Login with account with expensify card enabled with bank account added, and few members invited in workspace.
3. Go to workspace settings.
4. Tap expensify card.
5. Tap issue card.
6. Select a user -> physical card -> monthly.
7. Input an amount in the Set a limit amount page.
8. Go to confirmation page.
9. Navigate back to the Set a limit amount page.
10. Verify that the cursor caret is at the end of the amount, not at the begginning right after the currency symbol.

Steps for issue #50055:

1. Launch Android: Native app.
2. Log in with new account.
3. Go to Settings -> New workspace - More features - enable invoice.
4. Navigate to LHN.
5. Tap FAB -> Send invoice.
6. Enter an amount and tap Next.
7. Select a user.
8. Tap Next.
9. Enter company name and address.
10. Tap Send invoice.
11. Open invoice -> tap on Amount field.
12. Reopen the Amount field (repeat step 11).
13. Verify that the cursor caret is at the end of the amount, not at the begginning right after the currency symbol.

• 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 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 verified the translation was requested/reviewed 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.js 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 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.
• 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

Note

This PR fix only applies to Android: Native, none of the other platforms will be affected or work differently.

Card Limit Amount Issue	Invoice Amount Issue
android-card-limit.webm	android-invoice-amount.webm

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

[melvin-bot]

@shawnborton @mananjadhav One of you needs to 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]

[mananjadhav]

Reviewing

[shawnborton]

Videos look pretty good to me 👍

[shawnborton]

It does look like there is a slight delay once the cursor is shown right after the currency amount and then the cursor goes to the end of the input when the amount shows up. I'm not sure exactly what to make of that, maybe that's just an artifact of using RN here. cc @Expensify/design for input, and Jon curious if this is something that feels common across Android devices.

To be clear, this is a huge improvement from what we had before so I'm happy to move forward with what is shown here.

[ikevin127]

Note: The videos were taken on Android emulator which is pretty slow UI / UX wise compared to real Android devices. I will perform a build of this on my OnePlus 7T running Android 14 tomorrow to show how it looks on an actual device 🙌

Edit: I tested on real device and there's no difference in this case.

It does look like there is a slight delay once the cursor is shown right after the currency amount and then the cursor goes to the end of the input when the amount shows up.

I think this comes from the fact that the amount input's width is dynamic (grows with the input) which causes that glitchy effect on mount:

App/src/components/AmountTextInput.tsx

Lines 61 to 63 in a1196a6

	return (
	<TextInput
	autoGrow

To be clear, this is a huge improvement from what we had before so I'm happy to move forward with what is shown here.

From my side we're good to go move forward here with merging the PR.

[dubielzyk-expensify]

I'm not sure exactly what to make of that, maybe that's just an artifact of using RN here. cc @Expensify/design for input, and Jon curious if this is something that feels common across Android devices.

Nothing I've come across, but agree that it looks like a slow device/RN artefact. I would say we're still likely to see this on real devices though given lots of people out there don't have the newest technology. But still this feels a lot better so I'm okay with it too.

[mananjadhav]

Left with the final testing, will finish the checklist today.

[github-actions]

🚧 @mountiny has triggered a test build. You can view the workflow run here.

[mountiny]

Chatted with @hannojg and I believe the issue with the glitchy cursor should be fixed with this PR hopefully #50238

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/52734/index.html	https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/52734/index.html
Desktop 💻	Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/52734/NewExpensify.dmg	https://52734.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[mountiny]

@mananjadhav what is your ETA for the checklist?

[mananjadhav]

I have been trying to run the build locally and it's failing. I just finished a checklist for another PR and I didn't have the issue. Will delete all node_modules again and update the checklist in max few hours.

[mananjadhav]

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 tests pass on all platforms & I tested again on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
• 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 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
  • 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 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)
• 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.js or at the top of the file that uses the constant) are defined as such
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • 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
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • 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 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 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.
• 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: Native

android-send-invoice-amount-caret.mp4

android-card-limt-amount-caret.mp4

Android: mWeb Chrome

mweb-chrome-amount-caret.mov

iOS: Native

ios-card-amount-caret.mov

iOS: mWeb Safari

mweb-safari-amount-caret.mov

MacOS: Chrome / Safari

MacOS: Desktop

[shawnborton]

All good on my end, feel free to merge 👍

[OSBotify]

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

[github-actions]

🚀 Deployed to staging by https://github.com/aldo-expensify in version: 9.0.65-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	success ✅
🍎🔄 iOS HybridApp 🍎🔄	success ✅

[github-actions]

🚀 Deployed to production by https://github.com/chiragsalian in version: 9.0.65-5 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	failure ❌
🍎🔄 iOS HybridApp 🍎🔄	failure ❌