-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2023-10-24] [HOLD for payment 2023-10-23] [HOLD for payment 2023-10-23] Smart scanning header is broken #29626
Comments
Triggered auto assignment to @joekaufmanexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @thienlnam ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Split details receipt scan header is broken What is the root cause of that problem?In the SplitDetailsPage.js <MoneyRequestHeaderStatusBar is called without any arguments {isScanning && <MoneyRequestHeaderStatusBar />} What changes do you think we should make in order to solve the problem?Update the SplitDetailsPage.js to call with the required arguments {isScanning && <MoneyRequestHeaderStatusBar
title={translate('iou.receiptStatusTitle')}
description={translate('iou.receiptStatusText')}
shouldShowBorderBottom
/>} What alternative solutions did you explore? (Optional)N/A |
Offending PR #29201 |
cc @grgia |
@rushatgabhane will get $500 for internal review |
Sounds good! We'll issue payment after the 7 day waiting period. |
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-10-23. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.85-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-10-24. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
I see @rushatgabhane was actually already paid for this one on the PR. |
@rushatgabhane please complete your portion of the BZ checklist when you have a sec, and then we'll be all set to close this out! |
Pending completion of checklist |
Still pending completion |
@rushatgabhane, @thienlnam, @grgia, @joekaufmanexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Not overdue. @rushatgabhane is anything needed for BZ checklist here? |
Bumped in Slack |
Still pending input |
|
we can close the issue |
Sweet, TY! BZ checklist is all set. Payment was already issued on the PR, so closing as this one is good to go. |
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.3.84.0
Reproducible in staging?: Yes
Reproducible in production?: No
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:
+
action button and request moneyExpected Result:
Smart scanning header is visible
Actual Result:
Smart scanning header is broken
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Bug6237271_1697310012718.Recording__4999.mp4
MacOS: Desktop
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: