Skip to content

[$250] iOS - Chat - Big gap in the background when context menu is opened #54713

Closed

Description

@IuliiaHerets

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


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:

  1. Launch ND or hybrid app.
  2. Go to any chat.
  3. Send enough messages to make the chat scrollable.
  4. Send another message.
  5. Long press on the message in Step 4 > Reply in thread.
  6. Send a reply in thread.
  7. Delete the parent message.
  8. Go back to main chat.
  9. Tap on the composer to open keyboard if keyboard is not opened.
  10. Long press on [Deleted message].

Bug 2:

  1. Launch ND or hybrid app.
  2. Go to self DM.
  3. Track a manual expense.
  4. Tap on the composer to open keyboard if keyboard is not opened.
  5. 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.

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6704725_1735705353792.ScreenRecording_01-01-2025_12-21-44_1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021874487334985993620
  • Upwork Job ID: 1874487334985993620
  • Last Price Increase: 2025-01-15
Issue OwnerCurrent Issue Owner: @dominictb

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jan 1, 2025
  2. melvin-bot commented on Jan 1, 2025

    @melvin-bot

    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.

  3. melvin-bot commented on Jan 1, 2025

    @melvin-bot

    Triggered auto assignment to @carlosmiceli (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Jan 1, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Jan 1, 2025

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. added
    ExternalAdded to denote the issue can be worked on by a contributor
    and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Jan 1, 2025
  7. 17 remaining items

  8. carlosmiceli commented on Jan 10, 2025

    @carlosmiceli
    Contributor

    Sorry, been OOO for the past week! @kirillzyusko is the fix still being worked on?

  9. kirillzyusko commented on Jan 14, 2025

    @kirillzyusko
    Contributor

    @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.

  10. carlosmiceli commented on Jan 14, 2025

    @carlosmiceli
    Contributor

    @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?

  11. melvin-bot commented on Jan 15, 2025

    @melvin-bot

    @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!

  12. melvin-bot commented on Jan 15, 2025

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  13. carlosmiceli commented on Jan 15, 2025

    @carlosmiceli
    Contributor

    Follow up to my question above @kirillzyusko 🙏

  14. kirillzyusko commented on Jan 17, 2025

    @kirillzyusko
    Contributor

    @carlosmiceli let's close it. We are aware about the issue and will definitely fix it before making a PR as ready for review 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DesignEngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions