Skip to content

[$250] iOS - "x" clear button is very hard to toggle on iOS app #75966

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.63-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #75002
Email or phone of affected tester (no customers): applausetester+en@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: iPhone 15 Pro / 18.6.2
App Component: Workspace Settings

Action Performed:

  1. Access staging.new.expensify.com
  2. Log into a valid account with WS
  3. Create an expense in WS
  4. Click on the "Date" field
  5. Clear the date value by tapping on "X"

Expected Result:

Date should be cleared

Actual Result:

On the iPhone 15 Pro - Its very very difficult on my device to tap this "x" button, the hit box seems very small when compared to PROD

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

Image
Bug7012677_1764038751228.Very_dificult_to_clear_the_calendar_on_iphone_15_pro.mp4

Production behavior

Bug7012677_1764038751249.Prod_comparison.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021993430372160567230
  • Upwork Job ID: 1993430372160567230
  • Last Price Increase: 2025-12-09
  • Automatic offers:
    • huult | Contributor | 109790092
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @mallenexpensify

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 25, 2025
  2. melvin-bot commented on Nov 25, 2025

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (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. github-actions commented on Nov 25, 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.
  4. melvin-bot commented on Nov 25, 2025

    @melvin-bot

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

  5. melvin-bot commented on Nov 25, 2025

    @melvin-bot

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

  6. pecanoro commented on Nov 25, 2025

    @pecanoro
    Contributor

    I don't have a physical device so this is really hard to test for me since it works well in a emulator 😄

  7. 41 remaining items

  8. ZhenjaHorbach commented on Dec 17, 2025

    @ZhenjaHorbach
    Contributor

    This issue will be ready for payment on 23.12.2025

  9. ZhenjaHorbach commented on Dec 23, 2025

    @ZhenjaHorbach
    Contributor

    BugZero Checklist:

    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      I didn't find a suitable PR

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: NA

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    I'm not sure if tests are needed here, but ....

    Regression Test Proposal

    Test:

    1. Open the Expensify app.
    2. Log in to a valid account with a workspace.
    3. Create an expense in the workspace.
    4. Tap the "Date" field.
    5. Clear the date value by tapping the "X".
    6. Verify that the date is cleared and the button is easier to tap.

    Do we agree 👍 or 👎

    Zapier Logs Run ID: 00040eee-e62c-ac7b-c03a-77a6e17f5bd4
  10. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed
    ReviewingHas a PR in review
    on Dec 24, 2025
  11. mallenexpensify commented on Dec 24, 2025

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor: @huult paid $250 via Upwork
    Contributor+: @ZhenjaHorbach due $250 via NewDot

    Test case ^

    Thx!

  12. ZhenjaHorbach commented on Dec 24, 2025

    @ZhenjaHorbach
    Contributor

    Requested in ND!

  13. garrettmknight commented on Dec 29, 2025

    @garrettmknight
    Contributor

    $250 approved for @ZhenjaHorbach

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 contributorNeeds ReproductionReproducible steps needed

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions