[HOLD for payment 2024-04-15] BNP - Inconsistency in pointer position on android native and mWeb

[kbecciv]

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: v1.4.60-1
Reproducible in staging?: y
Reproducible in production?: new feature
Issue reported by: Applause - Internal Team

Action Performed:

1. Click on 'FAB'
2. Click on 'Request money'

Expected Result:

Pointer position should be consistent across platform. Pointer at end would good to clear zeros first before putting number.

Actual Result:

Android pointer position is start and mWeb and Web pointer position is at end

Workaround:

n/a

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6437968_1712235779049.Screen_Recording_20240404_160203_New_Expensify.mp4

Bug6437968_1712235676113.Screen_Recording_2024-04-04_at_4.00.43_in_the_afternoon.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @tgolen (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[github-actions]

👋 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:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[mountiny]

I believe this revert will fix it too #39610

[jasperhuangg]

@Expensify/applause Can we retest this since a fix was CP'd to staging in #39610?

[kavimuru]

@mountiny issue is fixed now.

Screen_Recording_20240405_162106_Chrome.mp4

Screen_Recording_20240405_162005_New.Expensify.mp4

[mountiny]

Thanks!

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.60-13 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Revert "35797-preserving-the-transactions-amounts-the-same-as-entered" #39610

If no regressions arise, payment will be issued on 2024-04-15. 🎊