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 #64085][$250] Composer - Keyboard overlaps the composer after selecting emoji #67022
Version Number: v9.1.85-2 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail:#65229 Email or phone of affected tester (no customers):duytestnguyen+employee@gmail.com Issue reported by: Applause Internal Team Device used: iPhone 11/iOS 18.5 App Component: Chat Report View
Action Performed:
Open iOS Native app
Tap on Reports tab
Tap on FAB
Create report
Send any msg to the report
Edit the message
Add an emoji from the emoji picker
Expected Result:
The composer will be refocused with the keyboard not overlapping or cutting off the composer
Actual Result:
The keyboard overlaps and covers totally the composer. With Android version, the keyboard will cut the composer a little.
👋 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.
Perf: Remove shouldAdjustScrollView to avoid heavy rerender #66849: Removed shouldAdjustScrollView and composer focus/blur handling in ReportScreen, so after the emoji-triggered refocus the keyboard appears without any scroll adjustment, letting it cover the composer.
fix: added report to AttachmentComposerModal #66734: Touched ReportActionCompose component while adding the report prop, which could inadvertently affect composer layout when reopened after emoji selection.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
Activity
github-actions commentedon Jul 24, 2025
👋 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 Jul 24, 2025
Triggered auto assignment to @jliexpensify (
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.melvin-bot commentedon Jul 24, 2025
Triggered auto assignment to @Gonals (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jul 24, 2025
💬 A slack conversation has been started in #expensify-open-source
jliexpensify commentedon Jul 24, 2025
I can repro this on a Pixel 7:
I think this is annoying but probably not a deploy blocker.
rushatgabhane commentedon Jul 24, 2025
@BlameGPT find offending pulls
BlameGPT commentedon Jul 24, 2025
Vibe check failed for these PRs 💅
If not above, check these
66 remaining items
melvin-bot commentedon Dec 16, 2025
This issue has not been updated in over 15 days. @Gonals, @jjcoffee, @jliexpensify eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
jliexpensify commentedon Dec 16, 2025
Still holding, other PR in review
melvin-bot commentedon Mar 5, 2026
@Gonals, @jjcoffee, @jliexpensify, this Monthly task hasn't been acted upon in 6 weeks; closing.
If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.
jliexpensify commentedon Mar 5, 2026
Still holding.
melvin-bot commentedon May 18, 2026
@Gonals, @mallenexpensify, @jjcoffee, this Monthly task hasn't been acted upon in 6 weeks; closing.
If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.