Skip to content

[Due for payment 2025-10-17] Chat - Composer is not focused after sending text with image #72142

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.28-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: #69523
Email or phone of affected tester (no customers): sdijsnoisjnosij@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Chat Report View

Action Performed:

  1. Go to staging.new.expensify.com
  2. Copy an image.
  3. Go to any chat.
  4. Type anything on the composer.
  5. Paste the image via CMD + V.
  6. Click Send or hit Enter.

Expected Result:

Composer will be focused after sending text with image.

Actual Result:

Composer is not focused after sending text with image.

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

Bug6969120_1759964112077.Screen_Recording_2025-10-09_at_06.47.24.mp4

View all open jobs on GitHub

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

    @melvin-bot

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

  4. github-actions commented on Oct 8, 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.
  5. melvin-bot commented on Oct 8, 2025

    @melvin-bot

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

  6. 17 remaining items

  7. melvin-bot commented on Oct 10, 2025

    @melvin-bot

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

  8. melvin-bot commented on Oct 10, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.28-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 2025-10-17. 🎊

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

  9. melvin-bot commented on Oct 10, 2025

    @melvin-bot

    @parasharrajat @mallenexpensify 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]

  10. melvin-bot commented on Oct 17, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  11. mallenexpensify commented on Oct 18, 2025

    @mallenexpensify
    Contributor

    Is this from a regression?

    I see it linked in the OP, unsure if payment is due to @parasharrajat

  12. parasharrajat commented on Oct 18, 2025

    @parasharrajat
    Member

    No payment here.

  13. mallenexpensify commented on Oct 20, 2025

    @mallenexpensify
    Contributor

    No payment here.

    Is that cuz of a regression? If so, was that issue paid out at 50% @parasharrajat ?

  14. parasharrajat commented on Oct 21, 2025

    @parasharrajat
    Member

    The parent issue is a tracking issue of the major refactor of many pages. So payment will be handled once that is completed. This is a side effect of one of the PRs, so I expect no payment here.

  15. mallenexpensify commented on Oct 21, 2025

    @mallenexpensify
    Contributor

    Thanks @parasharrajat, closing

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions