You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2025-01-15] Android - Chat - Emoji picker is jumpy when opened from context menu #54453
Version Number: 9.0.77-6 Reproducible in staging?: Y Reproducible in production?: N If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Email or phone of affected tester (no customers):applausetester+kh1311020@applause.expensifail.com Issue reported by: Applause - Internal Team Component: Chat Report View
Action Performed:
Launch ND or hybrid app
Open DM
Send a message to the DM if there is no message
Tap on the composer if keyboard is not up
Long tap on the message while keyboard is up
Tap Add reaction button
Might need to repeat Step 4 to 6 if the emoji picker is not jumpy
Expected Result:
Emoji picker will not be jumpy when opened from context menu when keyboard is opened
Actual Result:
Emoji picker is jumpy when opened from context menu when keyboard is opened
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Android: Standalone
Android: HybridApp
Android: mWeb Chrome
iOS: Standalone
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceBug6700988_1734891250375.Screen_Recording_20241223_021231_Expensify.mp4
👋 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:
Identify the pull request that introduced this issue and revert it.
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: Not needed as it is a improvement over existing code.
[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: NA
[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.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
melvin-bot commentedon Dec 22, 2024
Triggered auto assignment to @arosiclair (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Dec 22, 2024
👋 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:
melvin-bot commentedon Dec 22, 2024
💬 A slack conversation has been started in #expensify-open-source
lanitochka17 commentedon Dec 22, 2024
Production:
Uploading Screenrecorder-2024-12-22-20-33-16-287.mp4…
techievivek commentedon Dec 23, 2024
Doesn't seem to be a backend bug so removing the Deployblocker label from it.
25 remaining items
arosiclair commentedon Jan 8, 2025
@parasharrajat was the C+ for this
melvin-bot commentedon Jan 15, 2025
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
parasharrajat commentedon Jan 15, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[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: Not needed as it is a improvement over existing code.
[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: NA
[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.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: https://github.com/Expensify/Expensify/issues/462308
Regression Test Proposal
Test:
Do we agree 👍 or 👎
melvin-bot commentedon Jan 17, 2025
@arosiclair, @mallenexpensify, @kirillzyusko, @parasharrajat Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
kirillzyusko commentedon Jan 17, 2025
@danstepanov is working on this to fix 👀
parasharrajat commentedon Jan 17, 2025
This one is fixed. @kirillzyusko That is a different issue
mallenexpensify commentedon Jan 17, 2025
Contributor+: @parasharrajat due $250 via NewDot
Test Case
parasharrajat commentedon Jan 19, 2025
Payment requested as per #54453 (comment)
JmillsExpensify commentedon Jan 22, 2025
$250 approved for @parasharrajat