Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
2 of 6 tasks
izarutskaya opened this issue May 9, 2024 · 10 comments
Closed
2 of 6 tasks
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Needs Reproduction Reproducible steps needed

Comments

@izarutskaya
Copy link

izarutskaya commented May 9, 2024

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] 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): [email protected]
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

  1. Open the app and log in [email protected]
  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

@izarutskaya izarutskaya added DeployBlockerCash This issue or pull request should block deployment Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. DeployBlocker Indicates it should block deploying the API labels May 9, 2024
Copy link

melvin-bot bot commented May 9, 2024

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.

Copy link

melvin-bot bot commented May 9, 2024

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

@melvin-bot melvin-bot bot added Engineering Hourly KSv2 and removed Hourly KSv2 labels May 9, 2024
Copy link

melvin-bot bot commented May 9, 2024

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

@github-actions github-actions bot added Hourly KSv2 and removed Daily KSv2 labels May 9, 2024
Copy link
Contributor

github-actions bot commented May 9, 2024

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

@izarutskaya izarutskaya removed DeployBlockerCash This issue or pull request should block deployment DeployBlocker Indicates it should block deploying the API labels May 9, 2024
@izarutskaya
Copy link
Author

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

@arosiclair
Copy link
Contributor

arosiclair commented May 9, 2024

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.

@arosiclair arosiclair added Daily KSv2 and removed Engineering Hourly KSv2 labels May 9, 2024
@arosiclair
Copy link
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.

@arosiclair arosiclair added the Needs Reproduction Reproducible steps needed label May 9, 2024
@arosiclair arosiclair removed their assignment May 9, 2024
@MelvinBot
Copy link

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

@melvin-bot melvin-bot bot added the Overdue label May 13, 2024
@isabelastisser
Copy link
Contributor

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

@melvin-bot melvin-bot bot removed the Overdue label May 13, 2024
@arosiclair
Copy link
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
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Needs Reproduction Reproducible steps needed
Projects
None yet
Development

No branches or pull requests

4 participants