Skip to content

[Due for payment 2025-10-17] Attachment - Unable to send attachment after closing preview page via device back button #72145

Closed

Description

@mitarachim

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.2.28-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #69523
Email or phone of affected tester (no customers): sdijsnoisjnosij@gmail.com
Issue reported by: Applause Internal Team
Device used: Samsung Galaxy S25 FE / Android 16
App Component: Chat Report View

Action Performed:

  1. Launch Expensify app.
  2. Go to chat.
  3. Tap + > Add attachment > Choose file.
  4. Select any file.
  5. Tap device back button (on web, click browser back button).
  6. Tap + > Add attachment > Choose file.
  7. Select any file.

Expected Result:

Preview page will open.

Actual Result:

Nothing happens. No preview page opens.

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

Bug6969123_1759965021745.Screen_Recording_20251009_065328_Files.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @zanyrenney

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Oct 8, 2025
  2. melvin-bot commented on Oct 8, 2025

    @melvin-bot

    Triggered auto assignment to @kadiealexander (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 Oct 8, 2025

    @melvin-bot

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

  4. github-actions commented on Oct 8, 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.
  5. melvin-bot commented on Oct 8, 2025

    @melvin-bot

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

  6. aldo-expensify commented on Oct 9, 2025

    @aldo-expensify
    Contributor

    Reproduced in staging, can't reproduce in production 👍

  7. aldo-expensify commented on Oct 9, 2025

    @aldo-expensify
    Contributor

    This was caused by: #69523

  8. 28 remaining items

  9. melvin-bot commented on Oct 16, 2025

    @melvin-bot

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

  10. zanyrenney commented on Oct 16, 2025

    @zanyrenney
    Contributor

    Ah dang, I am OOO tomorrow. I will get to this on the Monday if that's okay team!

  11. melvin-bot commented on Oct 17, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@zanyrenney)

    • (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. melvin-bot commented on Oct 20, 2025

    @melvin-bot

    @zanyrenney Whoops! This issue is 2 days overdue. Let's get this updated quick!

  13. zanyrenney commented on Oct 22, 2025

    @zanyrenney
    Contributor

    Payment summary

    Contributor: @chrispader is from an agency-contributor and not due payment
    Reviewer: @parasharrajat owed $250 via NewDot - please request on ND.

  14. parasharrajat commented on Nov 9, 2025

    @parasharrajat
    Member

    Payment requested as per #72145 (comment)

  15. trjExpensify commented on Nov 17, 2025

    @trjExpensify
    Contributor

    approved $250 for @parasharrajat.

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

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions