Skip to content

IOS - Cut/Copy/Paste context menu blinks then disappears when double click in words in Task’s description #21812

Closed

Description

@kbecciv

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Open a task that has a description
  2. Click on Description to view the description’s details.
  3. Double-click on any word in the description.

Expected Result:

Cut/Copy/Paste context menu should be displayed

Actual Result:

Cut/Copy/Paste context menu blinks then disappears

Workaround:

Unknown

Platforms:

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

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.3.31-3
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Contex-menu-blink-and-disappears.1.MP4
ios.2806.mp4

Expensify/Expensify Issue URL:
Issue reported by: @tranvantoan-qn
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1687858087672039

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 28, 2023
  2. melvin-bot commented on Jun 28, 2023

    @melvin-bot

    Triggered auto assignment to @dylanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. melvin-bot commented on Jun 28, 2023

    @melvin-bot

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  4. hannojg commented on Jun 28, 2023

    @hannojg
    Contributor

    This is very likely the same issue as in:

    and will be fixed with:

    I will test this in a few minutes to verify 😊

    // EDIT: I can't reproduce this on the debug build from the main branch

  5. dylanexpensify commented on Jun 30, 2023

    @dylanexpensify
    Contributor

    Sounds like this was fixed then, yeah @hannojg? 😄

  6. dylanexpensify commented on Jul 3, 2023

    @dylanexpensify
    Contributor

    bump @hannojg?

  7. hannojg commented on Jul 3, 2023

    @hannojg
    Contributor

    Sorry, I edited the message instead of commenting 👀
    I wasn't able to reproduce the issue at all. That means I wasn't able to confirm whether the fix from the mentioned PR will fix this issue.

    We can test it again once the PR got merged?

  8. dylanexpensify commented on Jul 4, 2023

    @dylanexpensify
    Contributor

    Ahh sorry @hannojg! Didn't see that 🤦, any idea when PR will be merged and we can test again? Considering making this weekly

  9. hannojg commented on Jul 5, 2023

    @hannojg
    Contributor

    @dylanexpensify The PR got merged two days ago, you (or the issue creator) can either test from the main branch or wait until its on staging 😊

  10. dylanexpensify commented on Jul 7, 2023

    @dylanexpensify
    Contributor

    waiting for pr to be on staging!

  11. hannojg commented on Jul 7, 2023

    @hannojg
    Contributor

    @dylanexpensify Its on staging!

  12. dylanexpensify commented on Jul 10, 2023

    @dylanexpensify
    Contributor

    WOOOOOO! Will test today!

  13. hannojg commented on Jul 10, 2023

    @hannojg
    Contributor

    Awesome, let me know how it went! By now its also on production, so should be easy to test 😊

  14. dylanexpensify commented on Jul 12, 2023

    @dylanexpensify
    Contributor

    testing now!

  15. dylanexpensify commented on Jul 12, 2023

    @dylanexpensify
    Contributor

    fixed!! 🎉 ty @hannojg!!

  16. tranvantoan-qn commented on Jul 12, 2023

    @tranvantoan-qn

    Hi

    @dylanexpensify did you check the build for iOS on main or staging branch?

    I'm checking it too

  17. tranvantoan-qn commented on Jul 12, 2023

    @tranvantoan-qn

    I built the app with main and the issue seems to be fixed

    But may I be eligible for a reporting bonus? My report was valid and initially had no connection with the other tasks mentioned above.
    @dylanexpensify

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions