[Due for payment 2025-02-19] [$500] Android- Composer- Only haptic feedback but no paste menu when long tapping on the composer

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.48-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team

Action Performed:

Break down in numbered stepsPrecondition:

• User has copied any content on the device.

1. Launch New Expensify app.
2. Go to DM.
3. Long tap on the composer (do not make the keyboard appear).
4. Note that there is haptic feedback but no menu to paste when long tapping on the composer while keyboard is hidden.
5. Tap on the composer.
6. Dismiss keyboard by using device back navigation (device back button or swipe gesture to dismiss).
7. Long tap on the composer.
8. Note that now there is menu to paste.

Expected Result:

In Step 4, when the chat is opened for the first time, long tapping on the composer should bring up the menu to paste.

Actual Result:

In Step 4, when the chat is opened for the first time, there is no menu to paste when long tapping on the composer, and there is only haptic feedback.
In Step 8, the menu to paste only shows up after bringing up the keyboard and dismissing it.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6632256_1728681133881.1728680628113_Screen_Recording_20241012_050259_New_Expensify.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021846255346776510837
• Upwork Job ID: 1846255346776510837
• Last Price Increase: 2025-01-15
• Automatic offers:
• QichenZhu | Contributor | 105814058

Issue Owner

Current Issue Owner: @sakluger

[melvin-bot]

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

[github-actions]

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

[melvin-bot]

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

[melvin-bot]

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

[MarioExpensify]

The issue already happens in Production:

WhatsApp.Video.2024-10-14.at.17.48.30.mp4

Removing the DeployBlocker

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021846255346776510837

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @mollfpr (External)

[sakluger]

Waiting for proposals.

[sakluger]

Not overdue, we have no proposals yet.

[melvin-bot]

@sakluger, @mollfpr, @MarioExpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[melvin-bot]

@sakluger, @mollfpr, @QichenZhu, @MarioExpensify Eep! 4 days overdue now. Issues have feelings too...

[QichenZhu]

Still working on the PR.

[MarioExpensify]

@QichenZhu do you have an ETA?

[QichenZhu]

@mollfpr I wanted to test the PR further, but I’m not feeling well today. I’ll open it this week, but if it’s urgent, feel free to review it now.

cc @MarioExpensify

[MarioExpensify]

@QichenZhu we can wait, take your time! Thanks for the update!

[QichenZhu]

Proposal

Updated to include solutions for the iOS Safari issue discovered during PR phase.

[melvin-bot]

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

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.96-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Fix Composer context menu not opening #55647

If no regressions arise, payment will be issued on 2025-02-19. 🎊

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

• @mollfpr requires payment through NewDot Manual Requests
• @QichenZhu requires payment automatic offer (Contributor)

[melvin-bot]

@mollfpr @sakluger @mollfpr 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]

[sakluger]

@mollfpr could you please complete the BZ checklist here? Thanks!

[sakluger]

Summarizing payment on this issue:

Contributor: @QichenZhu $500, paid via Upwork
Contributor+: @mollfpr $500, request on Newdot

[mollfpr]

BugZero Checklist:

• [Contributor] Classify the bug:

Bug classification

Source of bug:

• 1a. Result of the original design (eg. a case wasn't considered)
• 1b. Mistake during implementation
• 1c. Backend bug
• 1z. Other:

Where bug was reported:

• 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
• 2b. Reported on staging (eg. found during regression or PR testing)
• 2d. Reported on a PR
• 2z. Other:

Who reported the bug:

• 3a. Expensify user
• 3b. Expensify employee
• 3c. Contributor
• 3d. QA
• 3z. Other:

• [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

  Link to comment: https://github.com/Expensify/App/pull/51172/files#r1962828838

• [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

  Link to discussion: Not a critical issue.

• [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

I think we don't need the regression test the code RCA is removed.

Regression Test Proposal Template

• [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

  Link to issue:

Regression Test Proposal

Precondition:

• Copy some text to the clipboard.

Test:

Do we agree 👍 or 👎

[sakluger]

Thanks! Payment summary is here: #50682 (comment)

[garrettmknight]

$500 approved for @mollfpr