[HOLD for payment 2024-06-28] [$250] Web - Categorizing - Folder icon in empty state screen is not centered

[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-79-2
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Issue found when executing PR #41344

Action Performed:

1. Go to staging.new.expensify.com
2. Create a new workspace
3. Delete all the categories
4. Go to FAB > Track expense > Manual
5. Track an expense
6. Click Categorize it from actionable whisper
7. Select the workspace from Step 2

Expected Result:

The folder icon in empty state screen should be centered

Actual Result:

The folder icon in empty state screen is not centered.
It is aligned a bit to the left

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

Bug6501950_1717527248050.bandicam_2024-06-05_02-50-57-513.1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~010e432e93c8345898
• Upwork Job ID: 1798238220399464448
• Last Price Increase: 2024-06-05
• Automatic offers:
• jjcoffee | Reviewer | 102614841
• tienifr | Contributor | 102614843

Issue Owner

Current Issue Owner: @abekkala

[melvin-bot]

Triggered auto assignment to @hayata-suenaga (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]

@hayata-suenaga 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

[hayata-suenaga]

missed this. working on it right now

[hayata-suenaga]

I don't think we have to block deploy for this. removing the deploy blocker label