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
[$250] iOS - Chat does not scroll down to show edit composer, suggestion list is hidden behind keyboard #64085
Version Number: 9.1.65-0 Reproducible in staging?: Y Reproducible in production?: 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):jsdonisjondjosd@gmail.com Issue reported by: Applause - Internal Team
Action Performed:
Precondition:
Have at least a workspace
Launch Expensify app
Open FAB > Create report
Send a message in the empty report
Long tap on the message > Edit comment
Tap outside the composer to close the keyboard
Tap on the edit composer
Note that the report view does not scroll down to reveal the edit composer
Type @ or :sm in the edit composer
Expected Result:
In Step 7, the report view will scroll down to reveal the edit composer when the edit composer is focused
In Step 8, the suggestion list will appear above the edit composer
Actual Result:
In Step 7, the report view does not scroll down to reveal the edit composer when the edit composer is focused
In Step 8, the suggestion list is partially hidden behind the keyboard
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceBug6858035_1749736661403.ScreenRecording_06-12-2025_21-52-15_1.mp4
defaults the viewPosition to 0. According to the documentation:
scrollToIndex: Scrolls to the item at the specified index such that it is positioned in the viewable area. viewPosition of 0 places it at the top, 1 at the bottom, and 0.5 centers it.
Cannot scroll to locations outside the render window without getItemLayout.
This works well for InvertedFlatList, but on the page experiencing this bug, we are using a regular FlatList. Thus, viewPosition: 0 causes the item to be scrolled to the top, which is not ideal when trying to reveal the composer near the bottom of the screen.
What changes do you think we should make in order to solve the problem?
When calling scrollToIndex in contexts using FlatList, explicitly pass the third parameter as false to ensure the item is scrolled into view at the bottom.
Additionally, the current logic attempts to ensure the keyboard is visible before calling scrollToIndex using InteractionManager.runAfterInteractions and requestAnimationFrame. However, these do not guarantee the keyboard is fully visible
changed the title [-]iOS - Chat does not scroll down to show edit composer, suggestion list is hidden behind keyboard[/-][+][$250] iOS - Chat does not scroll down to show edit composer, suggestion list is hidden behind keyboard[/+]on Jun 13, 2025
Hi there, we've been working on this feature for the last couple of months and I'd like to propose increasing the bounty of this issue with the following information.
Proposed amount to increase the price to: $1500 Multiple PRs:
Additional fixes:
Beyond implementing the new editing experience, several follow-up issues were identified and resolved:
Editing permissions in Admin-only chats
Keyboard behavior after cancelling edit mode
Composer focus/highlight state after editing
Autocorrection timing before message submission
These fixes addressed edge cases discovered during testing and rollout, extending well beyond the original implementation.
Scope expansion
The work evolved from introducing a new editing experience for small-screen devices into a broader refactor of the composer architecture. To support the feature cleanly, ReportActionCompose was restructured into more compositional components, enabling a dedicated EditOnlyReportActionCompose flow and improving maintainability of the editing system.
The final delivered scope was significantly larger than a straightforward UI change.
Core flow changes:
We modified the core functionality of the app, the way the user edits messages.
Deploy blockers audited:
The feature touched a core messaging experience and required auditing of related editing and composition flows to identify and resolve regressions before rollout. Multiple deploy-blocking issues were discovered and addressed through follow-up PRs.
Performance impact:
While performance optimization was not the primary goal, the work involved substantial refactoring of composition and editing components to support the new editing architecture while maintaining responsiveness and behavior consistency across platforms.
Test coverage:
Testing covered a large number of scenarios, including:
Editing messages on small-screen devices
Submitting edited messages with autocorrection enabled
Cancelling edits
Keyboard open/close behavior
Navigation interactions using device back buttons
Composer focus states after editing
Editing in Admin-only chats
Cross-platform behavior validation
Regression testing of existing compose and edit flows
Activity
melvin-bot commentedon Jun 12, 2025
Triggered auto assignment to @joekaufmanexpensify (
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.thelullabyy commentedon Jun 13, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
We already have logic to scroll to the editing message on focus:
App/src/pages/home/report/ReportActionItemMessageEdit.tsx
Lines 473 to 477 in 892fff8
The
scrollToIndexfunction being used:App/src/hooks/useReportScrollManager/index.native.ts
Line 19 in 892fff8
defaults the
viewPositionto0. According to the documentation:This works well for
InvertedFlatList, but on the page experiencing this bug, we are using a regularFlatList. Thus,viewPosition: 0causes the item to be scrolled to the top, which is not ideal when trying to reveal the composer near the bottom of the screen.What changes do you think we should make in order to solve the problem?
App/src/hooks/useReportScrollManager/index.native.ts
Line 13 in 892fff8
When calling
scrollToIndexin contexts usingFlatList, explicitly pass the third parameter asfalseto ensure the item is scrolled into view at the bottom.Additionally, the current logic attempts to ensure the keyboard is visible before calling
scrollToIndexusingInteractionManager.runAfterInteractionsandrequestAnimationFrame. However, these do not guarantee the keyboard is fully visibleApp/src/pages/home/report/ReportActionItemMessageEdit.tsx
Lines 473 to 477 in 892fff8
Instead, we should use the
waitForKeyboardToShowutility introduced here:withKeyboardState.tsx
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
joekaufmanexpensify commentedon Jun 13, 2025
Reproduced.
[-]iOS - Chat does not scroll down to show edit composer, suggestion list is hidden behind keyboard[/-][+][$250] iOS - Chat does not scroll down to show edit composer, suggestion list is hidden behind keyboard[/+]melvin-bot commentedon Jun 13, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021933546424749852553
melvin-bot commentedon Jun 13, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @shubham1206agra (
External)shubham1206agra commentedon Jun 13, 2025
@kirillzyusko Would you like to look into this? Since you implemented keyboard behavior in iOS.
kirillzyusko commentedon Jun 13, 2025
@shubham1206agra I'm currently busy with other work, but I believe @chrispader or @perunt can help here 😊🙌
chrispader commentedon Jun 16, 2025
i'll be able to look into this by the end of the week. If this needs to be handled more urgently, maybe @perunt or somebody else can work on this! 🙌🏼
176 remaining items
melvin-bot commentedon Jun 2, 2026
@hungvu193 Whoops! This issue is 2 days overdue. Let's get this updated quick!
hungvu193 commentedon Jun 4, 2026
I think this is ready for payment. I'll post the summary soon.
melvin-bot commentedon Jun 4, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)hungvu193 commentedon Jun 4, 2026
Hi there, we've been working on this feature for the last couple of months and I'd like to propose increasing the bounty of this issue with the following information.
Proposed amount to increase the price to: $1500
Multiple PRs:
ReportActionComposeinto more compositional components to allow for separateEditOnlyReportActionCompose#90915)Additional fixes:
Beyond implementing the new editing experience, several follow-up issues were identified and resolved:
These fixes addressed edge cases discovered during testing and rollout, extending well beyond the original implementation.
Scope expansion
The work evolved from introducing a new editing experience for small-screen devices into a broader refactor of the composer architecture. To support the feature cleanly, ReportActionCompose was restructured into more compositional components, enabling a dedicated EditOnlyReportActionCompose flow and improving maintainability of the editing system.
The final delivered scope was significantly larger than a straightforward UI change.
Core flow changes:
We modified the core functionality of the app, the way the user edits messages.
Deploy blockers audited:
The feature touched a core messaging experience and required auditing of related editing and composition flows to identify and resolve regressions before rollout. Multiple deploy-blocking issues were discovered and addressed through follow-up PRs.
Performance impact:
While performance optimization was not the primary goal, the work involved substantial refactoring of composition and editing components to support the new editing architecture while maintaining responsiveness and behavior consistency across platforms.
Test coverage:
Testing covered a large number of scenarios, including:
Files touched:
mallenexpensify commentedon Jun 5, 2026
@mountiny 👀 on @hungvu193 's proposed price increase above.
@hungvu193 thanks for posting a thorough breakdown.
mountiny commentedon Jun 5, 2026
Looks good to me, this was very complex change
mallenexpensify commentedon Jun 6, 2026
Payment Summary
Contributor+: @hungvu193 due $1500 via NewDot
Thx!
JmillsExpensify commentedon Jun 6, 2026
$1,500 approved for @hungvu193