Skip to content

[Due for payment 2025-05-28] [Due for payment 2025-05-27] Reports - Composer is blocked by bottom tab when expense report is opened from transaction thread #62196

Closed

Description

@jponikarchuk

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.1.46-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #61774
Email or phone of affected tester (no customers): applausetester+x31@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: iPhone 15 Pro Max / iOS 18.4
App Component: Search

Action Performed:

  1. Launch Expensify app.
  2. Go to workspace chat.
  3. Submit two expenses to the workspace chat.
  4. Go to Reports.
  5. Open one of the expenses from Step 3.
  6. Tap on the report header subtitle.

Expected Result:

The composer in the expense report will not be blocked by the bottom tab.

Actual Result:

The composer in the expense report is blocked by the bottom tab.
We can see a small part of the composer above the bottom tab, which shows that it is blocked.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

1.mp4
Image

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @bfitzexpensify

Activity

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

    @melvin-bot

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

  3. melvin-bot commented on May 16, 2025

    @melvin-bot

    Triggered auto assignment to @bfitzexpensify (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.

  4. melvin-bot commented on May 16, 2025

    @melvin-bot

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

  5. github-actions commented on May 16, 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. adamgrzybowski commented on May 16, 2025

    @adamgrzybowski
    Contributor

    I will take a look at that

  7. adamgrzybowski commented on May 16, 2025

    @adamgrzybowski
    Contributor

    @jponikarchuk I can't reproduce this problem. I tried on the web and iOS native. Is there something missing from my reproduction steps?

    Screen.Recording.2025-05-16.at.14.43.21.mov
  8. 15 remaining items

  9. changed the title [-]Reports - Composer is blocked by bottom tab when expense report is opened from transaction thread[/-] [+][Due for payment 2025-05-27] Reports - Composer is blocked by bottom tab when expense report is opened from transaction thread[/+] on May 20, 2025
  10. melvin-bot commented on May 20, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  11. melvin-bot commented on May 20, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.46-12 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2025-05-27. 🎊

    For reference, here are some details about the assignees on this issue:

  12. melvin-bot commented on May 20, 2025

    @melvin-bot

    @dukenv0307 @bfitzexpensify @dukenv0307 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  13. mountiny commented on May 20, 2025

    @mountiny
    Contributor

    Part of the project, we can close this one out as the regression testing and payments will be handled as part of traditional reports project

  14. changed the title [-][Due for payment 2025-05-27] Reports - Composer is blocked by bottom tab when expense report is opened from transaction thread[/-] [+][Due for payment 2025-05-28] [Due for payment 2025-05-27] Reports - Composer is blocked by bottom tab when expense report is opened from transaction thread[/+] on May 21, 2025
  15. melvin-bot commented on May 21, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.47-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2025-05-28. 🎊

    For reference, here are some details about the assignees on this issue:

  16. melvin-bot commented on May 21, 2025

    @melvin-bot

    @dukenv0307 @bfitzexpensify @dukenv0307 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions