Skip to content

[Due for payment 2026-04-14] Android - Report - User is auto scrolled up after returning from second added receipt. #84362

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.3.32.0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #83994
Email or phone of affected tester (no customers): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app)
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace.

  1. Open the Expensify app.
  2. Open any workspace chat.
  3. Create a manual expense.
  4. Open the just created expense.
  5. Add a receipt to the expense.
  6. After the receipt is added, return to report.
  7. Tap on the "Plus" button on receipt and add another receipt to report.
  8. Open the just added receipt and tap on the back button to return to report.
  9. Note that you are not scrolled up after returning.
  10. Tap on the "Plus" button on receipt again and add another receipt.
  11. Open the just added receipt and tap on the back button to return to report.
  12. Note that when you land on report, you are autoscrolled up.

Expected Result:

After returning from a receipt added to a report, the user should remain on the bottom of report.

Actual Result:

After returning to report from the second added receipt, user is autoscrolled up.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

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

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #83994

  3. melvin-bot commented on Mar 6, 2026

    @melvin-bot

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

  4. melvin-bot commented on Mar 6, 2026

    @melvin-bot

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

  5. github-actions commented on Mar 6, 2026

    @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. OSBotify commented on Mar 6, 2026

    @OSBotify
    Contributor

    🔍 Investigation Summary

    Classification: Frontend bug
    Causing PR: #83994 - "feat: allow multiple receipts to be attached to a single expense" by @TaduJR (High confidence)
    Related Issues: #81435

    Recommendation: REVERT

    PR #83994 introduced the ability to add multiple receipts to a single expense by adding action buttons (enlarge and add receipt) directly on the receipt image in MoneyRequestReceiptView. While the feature works as intended, it has introduced an auto-scroll regression on Android that disrupts the user experience. After adding the second receipt and returning to the report, users are unexpectedly scrolled to the top instead of remaining at the bottom of the thread where they were.

    This is a new feature that does not exist in production, so reverting will not remove any existing functionality from users.

    Labels: This is a frontend bug caused by an App PR. The issue is reproducible only on staging (not in production since the feature is new), but I am keeping both DeployBlockerCash and DeployBlocker labels as they were added by internal team members. Per the investigation protocol, I should not remove labels added by internal employees.

    📋 Detailed Analysis

    Evidence

    PR #83994 added two icon buttons overlaid on receipt images in MoneyRequestReceiptView:

    1. An enlarge button that opens the receipt modal
    2. An add receipt button that opens the attachment picker and posts files to the expense thread via addAttachmentWithComment

    The PR modified:

    • src/components/ReportActionItem/MoneyRequestReceiptView.tsx - Added the new buttons and attachment functionality
    • src/CONST/index.ts - Added button constants
    • src/styles/index.ts - Added button positioning styles

    Verification

    The bug report states that:

    • After adding the FIRST receipt and returning to the report, the user stays at the bottom (correct behavior)
    • After adding the SECOND receipt and returning to the report, the user is auto-scrolled to the top (bug)

    This matches the timeline: PR #83994 was merged on March 5, 2026, and is included in the staging deploy checklist (9.3.32-0). The issue was reported on March 6, 2026, and is marked as "N/A - new feature, doesn't exist in prod" - confirming this is a new feature introduced by this PR.

    Root Cause

    When the add receipt button is pressed, it calls addAttachmentWithComment() which creates a new report action in the thread. The InvertedFlatList (which powers the report actions view) is not maintaining the scroll position correctly after the second attachment is added. This appears to be a side effect of how the list handles scroll position when new items are added, particularly on Android.

    The behavior difference between the first and second receipt additions suggests there may be an issue with how the scroll key or scroll manager handles multiple rapid additions of new content to the inverted list.

  7. TaduJR commented on Mar 6, 2026

    @TaduJR
    Contributor

    Investigating...

  8. 25 remaining items

  9. ahmedGaber93 commented on Apr 13, 2026

    @ahmedGaber93
    Contributor

    BugZero Checklist:

    Regression Test Proposal

    Test:

    1. Open an expense report with enough messages to allow scrolling
    2. Scroll to the top
    3. Send an attachment using the compose bar
    4. Wait for the chat to automatically scroll to the new attachment
    5. Open the attachment
    6. Navigate back to the report
    7. Verify that you are still at the bottom of the report

    Do we agree 👍 or 👎

  10. melvin-bot commented on Apr 14, 2026

    @melvin-bot

    Issue is ready for payment but no BZ is assigned. @mallenexpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!

  11. melvin-bot commented on Apr 14, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  12. laurenreidexpensify commented on Apr 15, 2026

    @laurenreidexpensify
    Contributor
  13. TaduJR commented on Apr 15, 2026

    @TaduJR
    Contributor

    Applied @laurenreidexpensify

    Thanks!

  14. laurenreidexpensify commented on Apr 16, 2026

    @laurenreidexpensify
    Contributor

    Payment Summary

  15. flaviadefaria commented on Apr 29, 2026

    @flaviadefaria
    Contributor

    $250 approved for @ahmedGaber93

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

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions