Expensify / App

Welcome to New Expensify: a complete re-imagination of financial collaboration, centered around chat. Help us build the next generation of Expensify by sharing feedback and contributing to the code.
https://new.expensify.com
MIT License
3.36k stars 2.78k forks source link

[HOLD] [$500] [MEDIUM] Split bill – When Smartscan fails in Workspace, the Merchant field is empty and the amount is displayed as $0.00. #36046

Open m-natarajan opened 7 months ago

m-natarajan commented 7 months ago

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: 1.4.38-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. Go to https://staging.new.expensify.com/
  2. Login
  3. Navigate to the workspace chat
  4. Click on the + button > Split bill
  5. Use a receipt that will not fail the scan
  6. Continue to the final review page
  7. Create the expense
  8. When the scan request is complete click on the split preview to navigate to the split report

Expected Result:

The amount and merchant fields have been updated

Actual Result:

When Smartscan fails in Workspace, the Merchant field is empty and the amount is displayed as $0.00.

Workaround:

unknown

Platforms:

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

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/Expensify/App/assets/38435837/f19b6c2b-eef8-493d-9a84-c3bc49423c90

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01f4dd13f508eb66a6
  • Upwork Job ID: 1755275350909222912
  • Last Price Increase: 2024-02-27
youssef-lr commented 6 months ago

Same as above.

melvin-bot[bot] commented 6 months ago

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

abekkala commented 6 months ago

@twisterdotcom I'm ooo until April 08 - I'll be taking back any Open issues when I return


CURRENT STATUS:

On HOLD. If it comes off Hold before April 08 it will most likely require backend changes (Internal) see comment from @youssef-lr here

twisterdotcom commented 6 months ago

Still on HOLD apparently - gonna make it Weekly.

twisterdotcom commented 5 months ago

@abekkala is back today.

youssef-lr commented 5 months ago

Still held.

abekkala commented 5 months ago

still on hold

youssef-lr commented 5 months ago

Still held.

abekkala commented 4 months ago

not overdue, on hold

abekkala commented 4 months ago

on hold

abekkala commented 4 months ago

@youssef-lr are we still on hold for the backend fix on this one?

youssef-lr commented 3 months ago

Correct @abekkala, I'll try to get to this next week

abekkala commented 3 months ago

Still on hold

abekkala commented 3 months ago

@youssef-lr any updated info?

youssef-lr commented 3 months ago

I'm not able to prioritize this @abekkala since we paused working on vip-split, I think it can wait, I'm currently focusing on a issues from wave-collect, wave-control, and fast-apis.

abekkala commented 2 months ago

On HOLD

abekkala commented 2 months ago

still on hold for Youssef

abekkala commented 2 months ago

still on hold

abekkala commented 1 month ago

On hold

youssef-lr commented 1 month ago

Still held

youssef-lr commented 1 month ago

Still held.

abekkala commented 3 weeks ago

on hold

youssef-lr commented 1 week ago

Still held