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
When expense thread has message, report does not scroll correctly when menu/keyboard is opened #69758
Version Number: 9.2.1-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:#68932 Email or phone of affected tester (no customers):sjdiosjnojdsojsd@gmail.com Issue reported by: Applause Internal Team Device used: iPhone 15 Pro Max / iOS 18.6 App Component: Money Requests
Action Performed:
Launch Expensify app.
Go to workspace chat.
Submit two expenses to the workspace chat.
Open the expense report.
Open any transaction thread.
Send a message.
Dismiss the keyboard.
Long press on the message.
BUG 1 → The report view moves down and it reveals the empty background.
Dismiss the context menu.
Tap on the composer.
Scroll down to the sent message.
Dismiss the keyboard and tap on the composer again.
BUG 2 → The report view does not scroll down to the sent message when keyboard is opened.
Expected Result:
BUG 1: The report view in the background will not move when context menu is opened.
BUG 2: The report view will scroll down to the sent message when keyboard is opened.
Actual Result:
BUG 1: The report view moves down and it reveals the empty background when context menu is opened.
BUG 2: The report view does not scroll down to the sent message when keyboard is opened.
👋 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.
📣 @ingrammralph38! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
Activity
melvin-bot commentedon Sep 3, 2025
Triggered auto assignment to @sonialiap (
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 Sep 3, 2025
Triggered auto assignment to @iwiznia (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Sep 3, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Sep 3, 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 Sep 3, 2025
📣 @ingrammralph38! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format:
MonilBhavsar commentedon Sep 3, 2025
Removing DeployBlocker label as it's not related to API
arosiclair commentedon Sep 3, 2025
Fixed in v9.2.1.-10
melvin-bot commentedon Sep 22, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Sep 22, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.