[HOLD for payment 2024-07-10] [$250] Distance - Map pending not scaled and not fully visible when creating > 1 expenses

[lanitochka17]

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: 1.4.81-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4613584
Issue reported by: Applause - Internal Team

Issue found when executing PR #39243

Action Performed:

precondition: user a member of a workspace

1. Open the app and log in
2. Open the workspace chat
3. Create more than 1 distance expenses

Expected Result:

"Map pending" text is scaled in the report preview depending on the number of expenses

Actual Result:

"Map pending" is not fully visible, and it is displayed in multiple lines in the report preview.

Workaround:

Unknown

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

Bug6508409_1718040300016.video_2024-06-10_13-20-16.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~014fbedebd9a7bc999
• Upwork Job ID: 1801433825996987873
• Last Price Increase: 2024-06-14
• Automatic offers:
• ikevin127 | Reviewer | 102816669
• Krishna2323 | Contributor | 102816670

Issue Owner

Current Issue Owner: @JmillsExpensify

[melvin-bot]

Triggered auto assignment to @francoisl (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.

[lanitochka17]

@francoisl FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[lanitochka17]

We think that this bug might be related to #wave-collect - Release 1

[luacmartins]

I'm gonna demote this to NAB since it doesn't break anything and is a small issue