Skip to content

Chat - List of mentioned accounts cover the typed text when composer has multiple lines #46622

Closed

Description

@m-natarajan

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.15-4
Reproducible in staging?: y
Reproducible in production?: no
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4802024&group_by=cases:section_id&group_order=asc&group_id=290914
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

Action Performed:

  1. Go to any chat and tap to compose a message
  2. Add seven lines of text
  3. Type @

Expected Result:

The list of mentioned accounts do not cover the typed line

Actual Result:

The list of mentioned accounts cover the typed line and user can't see what its typed

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6558637_1722462614576.az_recorder_20240801_004522.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.
    DeployBlockerIndicates it should block deploying the API
    on Jul 31, 2024
  2. melvin-bot commented on Jul 31, 2024

    @melvin-bot

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

  3. melvin-bot commented on Jul 31, 2024

    @melvin-bot

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

  4. github-actions commented on Jul 31, 2024

    @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. m-natarajan commented on Jul 31, 2024

    @m-natarajan
    Author

    We think that this bug might be related to #vip-vsb

  6. roryabraham commented on Jul 31, 2024

    @roryabraham
    Contributor

    Maybe caused by #46091? Will create an AdHoc build of a revert to test

  7. kadiealexander commented on Aug 1, 2024

    @kadiealexander
    Contributor

    @roryabraham should I assign you?

  8. roryabraham commented on Aug 1, 2024

    @roryabraham
    Contributor

    no

  9. roryabraham commented on Aug 1, 2024

    @roryabraham
    Contributor
  10. roryabraham commented on Aug 1, 2024

    @roryabraham
    Contributor

    we merged a revert of #46091 after confirming the fix w/ an AdHoc build and Applause

  11. kavimuru commented on Aug 1, 2024

    @kavimuru

    Issue is fixed in the latest staging 9.0.15-8

    az_recorder_20240801_221019.mp4
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.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions