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
[Due for payment 2025-04-18] [$250] Android - Room -When editing mention, big space is displayed between suggestion and composer #57734
Version Number: 9.1.8-0 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both Email or phone of affected tester (no customers):ibellicotest+345@gmail.com Issue reported by: Applause Internal Team Device used: Motorola MotoG60 - Android 12 App Component: Other
Action Performed:
Open the Expensify app.
Open any room chat or create one if necessary.
Send a mention of any user that is not part of the room.
Send another mention of a different user that is not part of the room.
Return to inbox and open room again, so the system message for the first mention, appears again.
With the keyboard opened, long tap over the second mention and select "Edit Message"
Check the gap displayed between the mentions suggestions box and the edition composer.
Expected Result:
Suggestions box should be displayed above the edition composer, without a big space in between.
Actual Result:
When trying to edit a mention that is displayed below a system message of a different mention, a big space is displayed between suggestions box and edition composer.
changed the title [-]Android - Room -When editing mention, big space is displayed between suggestion and composer[/-][+][$250] Android - Room -When editing mention, big space is displayed between suggestion and composer[/+]on Mar 6, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.26-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@jjcoffee@OfstadC / @mallenexpensify@jjcoffee 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]
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:
[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.
[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:
Regression Test Proposal
Precondition:
Android-only, ideally test on devices of different sizes
Test:
Open any room chat or create one if necessary.
Send a mention of any user that is not part of the room.
Send another mention of a different user that is not part of the room.
Return to inbox and open room again, so the system message for the first mention, appears again.
With the keyboard opened, long tap over the second mention and select "Edit Message"
Verify that the suggestions box is displayed above the composer, without an unusually large gap.
@kavimuru That is unrelated to the original issue as it only deals with Android. Is there an existing issue for this, or can we create one to track the iOS version of this problem?
QA doesn't monitor GHs, if we need a bug report created, can you post in Slack and add the 'bug' emoji so QA can create a new one? Thx
Activity
melvin-bot commentedon Mar 4, 2025
Triggered auto assignment to @mallenexpensify (
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.mallenexpensify commentedon Mar 5, 2025
Think it's wrong vid in OP, asked about in `#qa
[-]Android - Room -When editing mention, big space is displayed between suggestion and composer[/-][+][$250] Android - Room -When editing mention, big space is displayed between suggestion and composer[/+]melvin-bot commentedon Mar 6, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021897461467419381223
melvin-bot commentedon Mar 6, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jjcoffee (
External)mallenexpensify commentedon Mar 6, 2025
Was able to repro, sent to pool, reckon it should be able to be fixed externally

zirgulis commentedon Mar 6, 2025
Hi I'm Povilas from Callstack and I would like to work on this issue
37 remaining items
melvin-bot commentedon Apr 11, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Apr 11, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.26-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-04-18. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Apr 11, 2025
@jjcoffee @OfstadC / @mallenexpensify @jjcoffee 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]
mallenexpensify commentedon Apr 14, 2025
@OfstadC thanks for keeping 👀 on, I unassigned ya.
jjcoffee commentedon Apr 17, 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:
[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: https://github.com/Expensify/App/pull/42630/files#r2048441024
[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:
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
melvin-bot commentedon Apr 18, 2025
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Apr 21, 2025
Contributor+: @jjcoffee due $250 via NewDot
Test case created
@jasperhuangg , I see this comment on the PR
QA doesn't monitor GHs, if we need a bug report created, can you post in Slack and add the 'bug' emoji so QA can create a new one? Thx
garrettmknight commentedon Apr 28, 2025
$250 approved for @jjcoffee