Skip to content

Compose Box - Character removed from compose box after selecting emoji #74844

Closed

Description

@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: 9.2.49-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: https://test-management.browserstack.com/projects/2219752/test-runs/TR-1937/folder/13176681/41236991/1008203443
Email or phone of affected tester (no customers): shussain+de1@applausemail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Navigate to a chat
  2. Open the emoji picker
  3. Select an emoji
  4. Enter a character in the compose box
  5. Observe the compose box content

Expected Result:

Typing a character after selecting an emoji should not remove the character

Actual Result:

After selecting an emoji, any character typed immediately gets removed from the compose box

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug7000880_1762886930907.2025-11-11_19-47-47.mp4

View all open jobs on GitHub

Activity

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

    @melvin-bot

    Triggered auto assignment to @johncschuster (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 11, 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 11, 2025

    @melvin-bot

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

  5. melvin-bot commented on Nov 11, 2025

    @melvin-bot

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

  6. chiragsalian commented on Nov 11, 2025

    @chiragsalian
    Contributor

    Regression from #67720
    Being handled by @LorenzoBloedow here

  7. izarutskaya commented on Nov 12, 2025

    @izarutskaya

    The issue is not reproducible on Windows 10/Chrome v9.2.54-0 PR:74921

    2025-11-12.14.06.42.mp4
  8. cristipaval commented on Nov 12, 2025

    @cristipaval
    Contributor

    Reverted the culprit

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions