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

Allow failed image/receipt uploads to be retried #54551

Open
wants to merge 27 commits into
base: main
Choose a base branch
from

Conversation

nyomanjyotisa
Copy link
Contributor

@nyomanjyotisa nyomanjyotisa commented Dec 25, 2024

Explanation of Change

Fixed Issues

$ #50507
PROPOSAL: #50507 (comment)

Tests

Same as QA Steps

  • Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

Test 1 (Replace Receipt):

  1. Create an expense to a workspace or another user
  2. Delete the receipt image & upload a new image for the receipt
  3. Disrupt the upload by losing the internet connection or using another method
  4. Verify that the receipt upload failed and display the error message: "There was an error uploading your receipt. Please try again or save the receipt to upload later."
  5. Dismiss the receipt
  6. Verify that the confirmation modal appears with the text: "Heads up! Dismissing this error will remove your uploaded receipt entirely. Are you sure?"
  7. Click on "Dismiss"
  8. Upload a new image for the receipt and repeat steps 3-4
  9. Click on "save the file"
  10. Verify that the image file is downloaded and the error message dismissed
  11. Repeat steps 8
  12. Click on "try again"
  13. Verify that the image uploads successfully.

Test 2 (Split expense):

  1. Split an expense to a workspace
  2. Disrupt the upload by losing the internet connection or using another method
  3. Verify that the receipt upload failed and display the error message: "There was an error uploading your receipt. Please try again or save the receipt to upload later."
  4. Dismiss the receipt
  5. Verify that the confirmation modal appears with the text: "Heads up! Dismissing this error will remove your uploaded receipt entirely. Are you sure?"
  6. Click on "Dismiss"
  7. Repeat steps 1-3
  8. Click on "save the file"
  9. Verify that the image file is downloaded and the error message dismissed
  10. Repeat steps 1-3
  11. Click on "try again"
  12. Verify that the receipt uploads successfully.

Test 3 (Track expense):

  1. Track an expense to a self DM
  2. Disrupt the upload by losing the internet connection or using another method
  3. Verify that the receipt upload failed and display the error message: "There was an error uploading your receipt. Please try again or save the receipt to upload later."
  4. Dismiss the receipt
  5. Verify that the confirmation modal appears with the text: "Heads up! Dismissing this error will remove your uploaded receipt entirely. Are you sure?"
  6. Click on "Dismiss"
  7. Repeat steps 1-3
  8. Click on "save the file"
  9. Verify that the image file is downloaded and the error message dismissed
  10. Repeat steps 1-3
  11. Click on "try again"
  12. Verify that the receipt uploads successfully.

Test 4 (Request Money - Scan):

  1. Create an expense to a workspace with a Receipt Scan
  2. Disrupt the upload by losing the internet connection or using another method
  3. Verify that the receipt upload failed and display the error message: "There was an error uploading your receipt. Please try again or save the receipt to upload later."
  4. Dismiss the receipt
  5. Verify that the confirmation modal appears with the text: "Heads up! Dismissing this error will remove your uploaded receipt entirely. Are you sure?"
  6. Click on "Dismiss"
  7. Repeat steps 1-3
  8. Click on "save the file"
  9. Verify that the image file is downloaded and the error message dismissed
  10. Repeat steps 1-3
  11. Click on "try again"
  12. Verify that the receipt uploads successfully.

Test 5 (Request Money - Manual):

  1. Manually create an expense to a workspace
  2. Disrupt the upload by losing the internet connection or using another method
  3. Verify that the receipt upload failed and display the generic error message: "Unexpected error submitting this expense. Please try again later."
  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android-Native.mp4
Android: mWeb Chrome
Android-mWeb.Chrome.mp4
iOS: Native
iOS-Native.mp4
iOS: mWeb Safari
iOS-mWeb.Safari.mp4
MacOS: Chrome / Safari
MacOS-Chrome.mp4
MacOS: Desktop
MacOS-Desktop.mp4

@nyomanjyotisa
Copy link
Contributor Author

nyomanjyotisa commented Dec 27, 2024

After checking again, there is a new issue on Android Native where the "Try Again" feature causes the receipt to appear uploaded in the app but fails during the actual upload process. This likely happens because the receipt is currently stored in the Downloads directory, and native Android cannot fetch images stored outside the app's private sandbox.

image

I think we need to explore an alternative approach for fetching images on Android. Still looking for a possible fix
This issue did not happen on the old PR because the change merged after I raised the PR

cc @dukenv0307 @sakluger

Android-Native.mp4

@dukenv0307
Copy link
Contributor

@nyomanjyotisa Have you found the solution?

@nyomanjyotisa
Copy link
Contributor Author

Yes, the issue on Android Native has been resolved

@nyomanjyotisa nyomanjyotisa marked this pull request as ready for review January 2, 2025 06:00
@nyomanjyotisa nyomanjyotisa requested a review from a team as a code owner January 2, 2025 06:00
@melvin-bot melvin-bot bot requested review from dukenv0307 and removed request for a team January 2, 2025 06:00
Copy link

melvin-bot bot commented Jan 2, 2025

@dukenv0307 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@dukenv0307
Copy link
Contributor

dukenv0307 commented Jan 3, 2025

@nyomanjyotisa What about this place:

errors: getReceiptError(transaction.receipt, transaction.filename || transaction.receipt?.filename, false, errorKey),
? Do we need to add action and retryParams?

filename?: string,
isScanRequest = true,
errorKey?: number,
action?: string,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should defined the action enum here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR updated

return isEmptyObject(receipt) || !isScanRequest
? ErrorUtils.getMicroSecondOnyxErrorWithTranslationKey('iou.error.genericCreateFailureMessage', errorKey)
: ErrorUtils.getMicroSecondOnyxErrorObject({error: CONST.IOU.RECEIPT_ERROR, source: receipt.source?.toString() ?? '', filename: filename ?? ''}, errorKey);
: ErrorUtils.getMicroSecondOnyxErrorObject(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In case users manually request money within receipt, the isScanRequest will be false, so the receipt error will not added to failureData. IMO, isEmptyObject(receipt) is enough, but not sure why the author add !isScanRequest check. Can you check this case?

Copy link
Contributor Author

@nyomanjyotisa nyomanjyotisa Jan 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, isEmptyObject(receipt) should be enough in this case. I’m not entirely sure why that additional check was included either. If I remove the !isScanRequest condition, this line will cause the generic error to display, resulting in a duplicate error message.

image

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How can you show these messages? I can't reproduce on my side

Screen.Recording.2025-01-06.at.11.18.41.mov

I think this line doesn't relate to isScanRequest. No matter what isScanRequest is, this error message is still added.

Copy link
Contributor

@dukenv0307 dukenv0307 Jan 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nyomanjyotisa But I think it's expected not to show receipt error in case manual request. So we should update the test steps.

For manual request: Show the generic message
For receipt request: Show the image error message

@@ -318,6 +321,56 @@ Onyx.connect({
},
});

type StartSplitBilActionParams = {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we will refactor the params in this issue so we shouldn't create the new type in this PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If that’s the case, how would you suggest handling retryParams in getReceiptError without introducing a new parameter like StartSplitBillActionParams? I believe the parameters haven’t been fully addressed in the mentioned issue yet right?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, you didn't introdude the new StartSplitBilActionParams, you just moved it to other place. So it's fine

@dukenv0307
Copy link
Contributor

I tested the retry and download feature on web and safari, they worked well but need to wait for @nyomanjyotisa to resolve the above comments before completing the tests on other platforms

@nyomanjyotisa
Copy link
Contributor Author

Do we need to add action and retryParams?

Correct me if I'm wrong, but I don't think action and retryParams are necessary there since the invoice doesn’t include a receipt

@dukenv0307
Copy link
Contributor

Correct me if I'm wrong, but I don't think action and retryParams are necessary there since the invoice doesn’t include a receipt

Yah, so I think we don't need to add retryParams here

@dukenv0307
Copy link
Contributor

@nyomanjyotisa Some tests are failed, can you pls check?

@nyomanjyotisa
Copy link
Contributor Author

Sorry for the late response. The failed test has been solved @dukenv0307

@dukenv0307
Copy link
Contributor

Reviewing...

? (JSON.parse(message.retryParams) as IOU.ReplaceReceipt | IOU.StartSplitBilActionParams | IOU.TrackExpense | IOU.RequestMoneyInformation)
: message.retryParams;

switch (message.action) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use ACTION_PARAMS const

<Text style={[StyleUtils.getDotIndicatorTextStyles(isErrorMessage)]}>{Localize.translateLocal('iou.error.receiptFailureMessage')}</Text>
<TextLink
style={[StyleUtils.getDotIndicatorTextStyles(), styles.link]}
onPress={() => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you pls define the new function for it (instead of anonymous func) ?

@dukenv0307
Copy link
Contributor

@nyomanjyotisa Pls let me know when it's ready for review. Thanks

@dukenv0307
Copy link
Contributor

@nyomanjyotisa friendly bump

@nyomanjyotisa
Copy link
Contributor Author

The PR has been updated. Could you please review it again, @dukenv0307?

@dukenv0307
Copy link
Contributor

dukenv0307 commented Jan 15, 2025

For handleRetryPress function, we should define it in libs. Then keep the src/components/DotIndicatorMessage.tsx as before

@dukenv0307
Copy link
Contributor

handleFileRetry are duplicated.

undefined,
undefined,
undefined,
policyTagList: undefined,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove undefined value

translate('iou.fieldPending'),
currentUserPersonalDetails.login,
currentUserPersonalDetails.accountID,
amount: 0,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should use default value in trackExpense, then remove the unnecessary value here

@dukenv0307
Copy link
Contributor

Pls refactor the trackExpense function call

@dukenv0307
Copy link
Contributor

@nyomanjyotisa Any updates?

@dukenv0307
Copy link
Contributor

@nyomanjyotisa bump

@nyomanjyotisa
Copy link
Contributor Author

Working on this today

@nyomanjyotisa
Copy link
Contributor Author

PR updated @dukenv0307

import useStyleUtils from '@hooks/useStyleUtils';
import useTheme from '@hooks/useTheme';
import useThemeStyles from '@hooks/useThemeStyles';
import {isReceiptError} from '@libs/ErrorUtils';
import fileDownload from '@libs/fileDownload';
import * as Localize from '@libs/Localize';
import {translateLocal} from '@libs/Localize';
import handleRetryPress from '@libs/ReceiptUploadRetryHandler/index';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
import handleRetryPress from '@libs/ReceiptUploadRetryHandler/index';
import handleRetryPress from '@libs/ReceiptUploadRetryHandler';

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants