Skip to content

[Due for payment 2026-01-15] [$250] Company card - "Can't downgrade workspace" content is very small when font size is small #74299

Closed

Description

@mitarachim

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.2.44-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #72926
Email or phone of affected tester (no customers): njsodisjodnsijdo@gmail.com
Issue reported by: Applause Internal Team
Device used: Samsung Galaxy S25 FE / Android 16
App Component: Workspace Settings

Action Performed:

Precondition:

  • Device font size is set to minimum.
  • Workspace is on Control plan and has two feeds (any) in Company card page.
  1. Launch Expensify app.
  2. Go to workspace settings > Overview.
  3. Tap Plan.
  4. Tap Collect.
  5. Tap Save.
  6. Tap Downgrade workspace.

Expected Result:

"Can't downgrade workspace" content will not be too small.

Actual Result:

"Can't downgrade workspace" content is very small compared to production (screenshots below).

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6994684_1762334477421.Screen_Recording_20251105_171708_Expensify.mp4

in Staging

Image

in Production

Image

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021986100785607720694
  • Upwork Job ID: 1986100785607720694
  • Last Price Increase: 2025-11-19
  • Automatic offers:
    • twilight2294 | Contributor | 109538749
    • situchan | Contributor | 109682151
Issue OwnerCurrent Issue Owner: @dylanexpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Nov 5, 2025
  2. melvin-bot commented on Nov 5, 2025

    @melvin-bot

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

  3. melvin-bot commented on Nov 5, 2025

    @melvin-bot

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

  4. melvin-bot commented on Nov 5, 2025

    @melvin-bot

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

  5. github-actions commented on Nov 5, 2025

    @github-actions
    Contributor

    👋 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.
  6. mitarachim commented on Nov 5, 2025

    @mitarachim
    Author

    Issue was found while executing QA for PR #72926

  7. 40 remaining items

  8. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jan 8, 2026
  9. changed the title [-][$250] Company card - "Can't downgrade workspace" content is very small when font size is small[/-] [+][Due for payment 2026-01-15] [$250] Company card - "Can't downgrade workspace" content is very small when font size is small[/+] on Jan 8, 2026
  10. melvin-bot commented on Jan 8, 2026

    @melvin-bot

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

  11. melvin-bot commented on Jan 8, 2026

    @melvin-bot

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

    If no regressions arise, payment will be issued on 2026-01-15. 🎊

    For reference, here are some details about the assignees on this issue:

  12. melvin-bot commented on Jan 8, 2026

    @melvin-bot

    @situchan @dylanexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  13. dylanexpensify commented on Jan 13, 2026

    @dylanexpensify
    Contributor

    Payment coming up!

  14. dylanexpensify commented on Jan 19, 2026

    @dylanexpensify
    Contributor

    Payment summary:

    Contributor: @twilight2294 $250 via Upwork
    Contributor+: @situchan $250 via Upwork

    Please apply/request!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions