Skip to content

[$250] Android-Room-After creating room, entering @ not showing contact suggestions #42766

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: 1.4.77-0
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://expensify.testrail.io/index.php?/tests/view/4585586
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. Launch app
  2. Tap fab -- start chat
  3. Create a new room
  4. Enter @ and wait few seconds
  5. Navigate to LHN
  6. Navigate to room again
  7. Keep cursor after @

Expected Result:

After creating room, entering @ must show contact suggestions

Actual Result:

After creating room, entering @ not showing contact suggestions but shown on revisit.

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

Add any screenshot/video evidence

Bug6495138_1716990722444.Screenrecorder-2024-05-29-19-16-06-795_compress_1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~016d65d15eadf82bb4
  • Upwork Job ID: 1795831001903484928
  • Last Price Increase: 2024-05-29
  • Automatic offers:
    • alitoshmatov | Reviewer | 102529959
    • ishpaul777 | Contributor | 102529960
Issue OwnerCurrent Issue Owner: @jliexpensify

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 May 29, 2024
  2. melvin-bot commented on May 29, 2024

    @melvin-bot

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

  3. melvin-bot commented on May 29, 2024

    @melvin-bot

    Triggered auto assignment to @jliexpensify (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 May 29, 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 May 29, 2024

    @m-natarajan
    Author

    @bondydaa FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

  6. m-natarajan commented on May 29, 2024

    @m-natarajan
    Author

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

  7. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on May 29, 2024
  8. 25 remaining items

  9. tomekzaw commented on Jun 5, 2024

    @tomekzaw
    Contributor

    There were no Android-specific changes between react-native-live-markdown@0.1.70 and 0.1.76 so I have no idea what could have caused this regression.

    edit: I've bumped Live Markdown to 0.1.76 and I cannot reproduce the original problem with suggestion box, it works for me.

  10. fabOnReact commented on Jun 6, 2024

    @fabOnReact
    Contributor

    I quote Skalakid comment.

    After a quick investigation I found out that the live markdown parser is using a different commit of expensify-common than E/App. Live Markdown parser uses a newer version of ExpeniMark that contains changes that block blockquote creation without space after

    I will create PR that bumps the version in the Expensify App
    I pulled the latest main and E/App has a newer version of expensify-common than live markdown. I can't reproduce this issue now

    57d8b2b

    Maybe with the latest version of expensify-common and react-native-live-markdown the issue will not reproduce anymore. I will verify this on Monday (unluckily now I have other commitments). Thanks

  11. melvin-bot commented on Jun 7, 2024

    @melvin-bot

    @bondydaa, @jliexpensify, @ishpaul777 Whoops! This issue is 2 days overdue. Let's get this updated quick!

  12. bondydaa commented on Jun 10, 2024

    @bondydaa
    Contributor

    Thanks @tomekzaw and @fabOnReact let me know if you need anything from me.

  13. fabOnReact commented on Jun 11, 2024

    @fabOnReact
    Contributor

    I tested and I can not reproduce this issue anymore.

    CLICK TO OPEN TESTS RESULTS

    Screen.Recording.2024-06-11.at.11.59.08.AM.mov

    CLICK TO OPEN TESTS RESULTS

  14. ishpaul777 commented on Jun 11, 2024

    @ishpaul777
    Contributor

    @jliexpensify Can we release bounty for the issue please

  15. melvin-bot commented on Jun 11, 2024

    @melvin-bot

    @bondydaa, @jliexpensify, @ishpaul777 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

  16. jliexpensify commented on Jun 12, 2024

    @jliexpensify
    Contributor

    There wasn't an actual regression here right? Also, what's the original PR? Melvin hasn't updated the date so just want to check everything has been deployed.

  17. melvin-bot commented on Jun 12, 2024

    @melvin-bot

    @bondydaa @jliexpensify @ishpaul777 this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

  18. jliexpensify commented on Jun 12, 2024

    @jliexpensify
    Contributor

    PR - #42843

    Will pay out today, confirmed with Bondy no checklist needed. Payment summary.

  19. jliexpensify commented on Jun 13, 2024

    @jliexpensify
    Contributor

    Paid and job closed.

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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions