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 - Big gap in the background when context menu is opened #54713
Version Number: 9.0.80-1 Reproducible in staging?: Yes Reproducible in production?: No If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both If this was caught during regression testing, add the test name, ID and link from TestRail: Exp Email or phone of affected tester (no customers):applausetester+394034@applause.expensifail.com Issue reported by: Applause Internal Team Device used: iPhone 15 Pro Max / iOS 18.2 App Component: Chat Report View
Action Performed:
Bug 1:
Launch ND or hybrid app.
Go to any chat.
Send enough messages to make the chat scrollable.
Send another message.
Long press on the message in Step 4 > Reply in thread.
Send a reply in thread.
Delete the parent message.
Go back to main chat.
Tap on the composer to open keyboard if keyboard is not opened.
Long press on [Deleted message].
Bug 2:
Launch ND or hybrid app.
Go to self DM.
Track a manual expense.
Tap on the composer to open keyboard if keyboard is not opened.
Long tap on Concierge message.
Expected Result:
There will be no big gap in the background when context menu is opened.
Actual Result:
There is a big gap in the background when context menu 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.
@carlosmiceli that issue was caused by a PR that was merged. However that PR was reverted, so the issue is not present in current prod/staging builds. We'll keep this ticket in mind when we open a new PR.
@carlosmiceli@shawnborton@MitchExpensify@dominictb this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
Activity
melvin-bot commentedon Jan 1, 2025
Triggered auto assignment to @MitchExpensify (
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 Jan 1, 2025
Triggered auto assignment to @carlosmiceli (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jan 1, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jan 1, 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:
17 remaining items
carlosmiceli commentedon Jan 10, 2025
Sorry, been OOO for the past week! @kirillzyusko is the fix still being worked on?
kirillzyusko commentedon Jan 14, 2025
@carlosmiceli that issue was caused by a PR that was merged. However that PR was reverted, so the issue is not present in current prod/staging builds. We'll keep this ticket in mind when we open a new PR.
carlosmiceli commentedon Jan 14, 2025
@kirillzyusko Ah, understood. Are you saying that we can close this issue then? Or that you'll close it once the new PR is merged?
melvin-bot commentedon Jan 15, 2025
@carlosmiceli @shawnborton @MitchExpensify @dominictb this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
melvin-bot commentedon Jan 15, 2025
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
carlosmiceli commentedon Jan 15, 2025
Follow up to my question above @kirillzyusko 🙏
kirillzyusko commentedon Jan 17, 2025
@carlosmiceli let's close it. We are aware about the issue and will definitely fix it before making a PR as ready for review 🙂