Checkmark appears in incorrect position for paid IOU thread

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Request money from user A to user B
2. From user B settle that amount
3. Open the IOU thread
4. Click on the IOU paid card

Expected Result:

Green checkmark should be beside the amont

Actual Result:

Appears at the right end

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

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

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: v1.3.35-5
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @manjesh-yadav
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1688099500775589

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @sophiepintoraetz (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[OSBotify]

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

[melvin-bot]

Triggered auto assignment to @marcochavezf (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[kushu7]

Its regression from https://github.com/Expensify/App/pull/21769/files
flex1 was added in this PR.

[sophiepintoraetz]

I'm able to reproduce this! Will stay assigned so I can pay out the reporting bonus

[sophiepintoraetz]

cc @dukenv0307 @cristipaval @mananjadhav - seeing as you were involved with the PR regression (thank you @kushu7!)

[mananjadhav]

@sophiepintoraetz I think this was fixed #21936 but not deployed to staging.

[cristipaval]

yes, it was fixed but not deployed yet in the PR linked above. Also, we can safely remove the deploy blocker label since it is a styling issue that does not block the user at all.

[sophiepintoraetz]

Yup - fixed

[manjesh-yadav]

I'm able to reproduce this! Will stay assigned so I can pay out the reporting bonus

As this issue is closed I should be compensated for reporting bonus @sophiepintoraetz

[sophiepintoraetz]

offer sent @manjesh-yadav

[manjesh-yadav]

Offer accepted @sophiepintoraetz