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

[$500] EReceipt - Card section in EReceipt for Expensify transaction is blank #35036

Closed
1 of 6 tasks
kavimuru opened this issue Jan 24, 2024 · 21 comments
Closed
1 of 6 tasks
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 External Added to denote the issue can be worked on by a contributor Help Wanted Apply this label when an issue is open to proposals by contributors retest-weekly Apply this label if you want this issue tested on a Weekly basis by Applause

Comments

@kavimuru
Copy link

kavimuru commented Jan 24, 2024

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Wave/Project Suggestion : #wave5-free-submitters

Version Number: 1.4.30-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

Action Performed:

  1. Log in to account with Expensify Card transaction (tester@applausecard.expensifail.com
    ).
  2. Go to workspace chat with the transaction (https://staging.new.expensify.com/r/4612388815642526
    ).
  3. Open transaction that has card number in the receipt (identify from Old Dot). (https://staging.new.expensify.com/r/4366841222340859
    )
  4. Open the receipt.

Expected Result:

The card section shows the card detail.

Actual Result:

The card section is blank.

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

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

Add any screenshot/video evidence

Bug6352936_1706074445794.20240124_115745.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0143ec88c80eec0c3c
  • Upwork Job ID: 1750052229901262848
  • Last Price Increase: 2024-02-07
@kavimuru kavimuru added External Added to denote the issue can be worked on by a contributor Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Jan 24, 2024
@melvin-bot melvin-bot bot changed the title EReceipt - Card section in EReceipt for Expensify transaction is blank [$500] EReceipt - Card section in EReceipt for Expensify transaction is blank Jan 24, 2024
Copy link

melvin-bot bot commented Jan 24, 2024

Job added to Upwork: https://www.upwork.com/jobs/~0143ec88c80eec0c3c

Copy link

melvin-bot bot commented Jan 24, 2024

Triggered auto assignment to @adelekennedy (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Jan 24, 2024
Copy link

melvin-bot bot commented Jan 24, 2024

Triggered auto assignment to Contributor-plus team member for initial proposal review - @Ollyws (External)

@AzhanJaved
Copy link

Hi there,
I'm a React Native developer with 5+ years of experience, eager to solve the elusive case of the blank card section in Expensify EReceipts (issue #35036). Having delved into the clues (comments, video evidence), I propose a two-pronged investigation to unveil the culprit and restore card information with aplomb.

My Proposed Solution:

  1. Data Detective:
    Following the Breadcrumbs: Employing debugging tools, I'll track the data flow, sniffing out any missing information between the backend and the EReceipt. APIs, authentication, and parsing will be under my digital microscope.
    Error Trapper: Unit tests will be my secret weapon, capturing any rogue errors or edge cases that might be hiding the card details.
  2. Conditional Conundrum:
    Logic Lens: I'll scrutinize the component responsible for displaying the card information, dissecting its conditional rendering logic for inconsistencies or missing variables. React DevTools will be my trusty sidekick, visualizing the component hierarchy and state.
    Test the Hypothesis: Through comprehensive unit tests, I'll verify that the card information displays correctly under various scenarios, ensuring a permanent fix.

I'm eager to delve deeper into the investigation and discuss my findings in the GitHub issue. Looking forward to your response.

Regards,
Arbaz

Copy link

melvin-bot bot commented Jan 24, 2024

📣 @AzhanJaved! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

  1. Make sure you've read and understood the contributing guidelines.
  2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
  3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
  4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
    Screen Shot 2022-11-16 at 4 42 54 PM
    Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

@AzhanJaved
Copy link

Contributor details
Your Expensify account email: muhammadazhanjaved9191@gmail.com
Upwork Profile Link: https://www.upwork.com/fl/~01ffc7b6b8084ce2fd

Copy link

melvin-bot bot commented Jan 24, 2024

⚠️ Missing/invalid email or upwork profile link. Please make sure you add both your Expensify email and Upwork profile link in the format specified.

@Ollyws
Copy link
Contributor

Ollyws commented Jan 24, 2024

@AzhanJaved Thanks for the interest, please have a look at the contributing guide for details on how to construct a proposal.

@AzhanJaved
Copy link

AzhanJaved commented Jan 24, 2024 via email

@melvin-bot melvin-bot bot added the Overdue label Jan 29, 2024
@dragnoir
Copy link
Contributor

@Ollyws do you think we can have an Expensify Card transaction account for testing?

@Ollyws
Copy link
Contributor

Ollyws commented Jan 29, 2024

I will have a look there may be a way to simulate it on the front end.

@melvin-bot melvin-bot bot removed the Overdue label Jan 29, 2024
@dragnoir
Copy link
Contributor

I can simulate using this https://expensify.slack.com/archives/C01GTK53T8Q/p1705450786474319?thread_ts=1705450150.383239&cid=C01GTK53T8Q

but I can't reproduce the issue.

@melvin-bot melvin-bot bot added the Overdue label Jan 31, 2024
Copy link

melvin-bot bot commented Jan 31, 2024

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

@Ollyws
Copy link
Contributor

Ollyws commented Feb 1, 2024

@dragnoir If you create a normal money request, find the transaction ID for that request then navigate to the transaction page and paste Onyx.merge("transactions_<TRANSACTIONID>", { hasEReceipt: true }); into the console it should be reproducible.

Screen.Recording.2024-02-01.at.13.03.32.mov

@melvin-bot melvin-bot bot removed the Overdue label Feb 1, 2024
@dragnoir
Copy link
Contributor

dragnoir commented Feb 1, 2024

@Ollyws thx for your help. But this doesn't reproduce the issue as I tested.

@melvin-bot melvin-bot bot added the Overdue label Feb 5, 2024
Copy link

melvin-bot bot commented Feb 6, 2024

@Ollyws, @adelekennedy Huh... This is 4 days overdue. Who can take care of this?

@adelekennedy
Copy link

I can't reproduce this either, going to add the retest weekly label

@melvin-bot melvin-bot bot removed the Overdue label Feb 6, 2024
@adelekennedy adelekennedy added the retest-weekly Apply this label if you want this issue tested on a Weekly basis by Applause label Feb 6, 2024
Copy link

melvin-bot bot commented Feb 7, 2024

@Ollyws @adelekennedy this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

Copy link

melvin-bot bot commented Feb 7, 2024

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

@melvin-bot melvin-bot bot added the Overdue label Feb 9, 2024
@adelekennedy
Copy link

still not reproducing

@melvin-bot melvin-bot bot added Overdue and removed Overdue labels Feb 9, 2024
Copy link

melvin-bot bot commented Feb 13, 2024

@Ollyws, @adelekennedy Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

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 External Added to denote the issue can be worked on by a contributor Help Wanted Apply this label when an issue is open to proposals by contributors retest-weekly Apply this label if you want this issue tested on a Weekly basis by Applause
Projects
None yet
Development

No branches or pull requests

5 participants