iOS/Android - Categorize it - Paragraph in success message has different alignment (left-aligned)

[IuliiaHerets]

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: 9.0.68-4
Reproducible in staging?: Y
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Email or phone of affected tester (no customers): applausetester+232803@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

Precondition:

• Device font size should be small.
• Account has no workspace.

1. Launch ND or hybrid app.
2. Create a new workspace.
3. Go to workspace settings > More features.
4. Enable Report fields.
5. Tap Upgrade.
6. Note that the paragraph in the success message is center-aligned.
7. Delete the workspace.
8. Go to self DM.
9. Track a manual expense.
10. Tap Categorize it.
11. Tap Upgrade.

Expected Result:

The paragraph in the success message should be consistent with Step 6, so it should be center-aligned.

Actual Result:

The paragraph in the success message is not consistent - it is left-aligned.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6679913_1732880954130.ScreenRecording_11-29-2024_20.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @muttmuure (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

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

[rlinoz]

No need to block on this, removing the label.