Skip to content

Conversation - Receipt image does not load and download file not working in old conversation #41915

Closed

Description

@izarutskaya

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: v1.4.72-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers): nhut.nguyenminh.it+2@gmail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

  1. Open the app and log in nhut.nguyenminh.it+2@gmail.com
  2. Go to any conversation and have a owed message (Paid + have with image) or create a new scan expense
  3. Tap on detail
  4. Try to tap on image

Expected Result:

Receipt image can be open and download

Actual Result:

Receipt image does not load and the download file not working in the conversation
Also console error appier

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6437510_1712197873683.Screen_Recording_2024-04-04_at_09.28.03.mp4
Recording.2444.mp4

Screenshot 2024-05-09 165156

View all open jobs on GitHub

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 May 9, 2024
  2. melvin-bot commented on May 9, 2024

    @melvin-bot

    Triggered auto assignment to @isabelastisser (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 May 9, 2024

    @melvin-bot

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

  4. melvin-bot commented on May 9, 2024

    @melvin-bot

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open Staging deploy checklist to see the list of PRs included in this release, then work quickly on the following:

    1. If you find which PR caused the issue/bug, you can reassign it to the person responsible for it.
      • If the author is OOO or won’t get online before the daily deploy is due, you are responsible for finding the best fix/path forward. Don’t hesitate to ask for help!
    2. Try to reproduce the issue, if the bug is on production, remove the DeployBlocker label but stay assigned to fix it (or find out which PR broke it to get help from the author).
      • You can adjust the urgency of the issue to better represent the gravity of the bug.
      • If the issue is super low priority, feel free to un-assign yourself.
      • Be careful with PHP warnings, sometimes it is more complex than just adding a null coalescing operator as they might be uncovering some bigger bug.
      • If it was a one-off issue that requires no action (for example, Bedrock was down or it is a duplicated issue), you can close it.

    Remember rule #2: Never un-assign yourself from a real DeployBlocker unless you are 100% sure someone else is assigned and will take care of it.

  5. github-actions commented on May 9, 2024

    @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. 1 remaining item

  7. izarutskaya commented on May 9, 2024

    @izarutskaya
    Author

    I couldn't upload the image for this issue here because it's more than 10 MB

  8. arosiclair commented on May 9, 2024

    @arosiclair
    Contributor

    Not able to reproduce on v1.4.72-0 with my personal account. I agree that this isn't a deploy blocker and might be an issue specific to that account/receipt.

  9. arosiclair commented on May 9, 2024

    @arosiclair
    Contributor

    I supportal'd into their account can see and download the receipt on OldDot. Unfortunately I can't get anything to load when supportal'd into NewDot. This is probably a legit bug but needs repro.

  10. removed their assignment
    on May 9, 2024
  11. MelvinBot commented on May 9, 2024

    @MelvinBot
    Contributor

    This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

  12. isabelastisser commented on May 13, 2024

    @isabelastisser
    Contributor

    I can't reproduce this either. I tried to supportal into NewDot but it crashed. What should I do next, @arosiclair ? thanks!

  13. arosiclair commented on May 13, 2024

    @arosiclair
    Contributor

    I think it's okay to close this out if it's not reproducible for you either.

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.DailyKSv2Needs ReproductionReproducible steps needed

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions