Fix - Distance-Distance field is stuck on pending... and no error shown when updating of waypoints fails

[FitseTLT]

Details

Fixed Issues

$ #52248
PROPOSAL: #52248 (comment)

Tests

1. Create a distance expense
2. Open the request details page
3. Open Testing preferences and turn on "Force offline" and "Simulate failing network requests"
4. Press on distance menu and change the waypoints by either adding a waypoint or dragging and reshuffling the waypoints
5. Click Save button
6. Open Testing preferences and turn off "Force offline"
7. Go to the request details page
8. Verify that after a while, it shows "Unexpected error editing this expense" and the waypoints are reverted to the previous value
9. Verify that there is a dismissable error shown below the map

• Verify that no errors appear in the JS console

Offline tests

Same as above

QA Steps

1. Workspace has at least two distance rates.
2. Go to workspace chat.
3. Submit a distance expense with distance rate A.
4. Go to workspace settings > Distance rates.
5. Delete distance rate A (from Step 3).
6. Go to workspace chat.
7. Go to transaction thread of the distance expense.
8. Click Distance.
9. Edit the distance and save it.
10. Dismiss the error "The selected rate has been deleted"
11. Verify that the distance receipt and distance field has reverted to the previous value.

[x] 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
  • 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 verified the translation was requested/reviewed 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
  • 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.js 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(themeColors.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 form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label 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.
• 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

Untitled.Project2.mp4

Android: mWeb Chrome

aw.mp4

iOS: Native

ip.mp4

iOS: mWeb Safari

iw.mp4

MacOS: Chrome / Safari

w.mp4

MacOS: Desktop

d.mp4

[melvin-bot]

@hoangzinh 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]

[FitseTLT]

BTW @hoangzinh simulate failing networks is not reliable. It makes the request fail immediately and the values will be reverted and error displayed but after a while it sends the request and the change will be pushed from the BE.
You can easily test by passing wrong params here

App/src/libs/actions/IOU.ts

Line 3229 in 10a75ac

API.write(WRITE_COMMANDS.UPDATE_MONEY_REQUEST_DISTANCE, params, onyxData);

but I am more concerned for QA because they can't alter the code so if you have a better QA testing steps please forward it 👍
And also what do you think about showing the pending map view when there is waypoints error? Now even on error we are showing the map if the coordinates are fetched and available from the BE.

[hoangzinh]

what do you think about showing the pending map view when there is waypoints error

Sorry for leaving for a while. @FitseTLT, I recall when there is waypoints error, we revert backs to previous waypoints. It makes sense to keep the previous map, doesn't it?

[FitseTLT]

what do you think about showing the pending map view when there is waypoints error

Sorry for leaving for a while. @FitseTLT, I recall when there is waypoints error, we revert backs to previous waypoints. It makes sense to keep the previous map, doesn't it?

We currently have two ways to show the map:

1. Map image file returned from BE
2. Via Mapbox map component using the route.coordinates and we show it when we have pending waypoints or there are errors
   

   App/src/components/ReportActionItem/ReportActionItemImage.tsx

   Line 88 in b818d54

   const showMapAsImage = isDistanceRequest && (hasErrors || hasPendingWaypoints);

   
   so now in our case the error happened due to failing requests and when you go back online and there are no coordinates it will show the pending map view and when you open the distance page it automatically fetches the coordinates and populates the transaction so the map will appear in money request view. WDYT about this behaviour of the map appearing and disappearing like in the video

2024-12-03.19-20-11.mp4

[hoangzinh]

I see @FitseTLT. At first glance, I think we should avoid it. But let me take a look deeper

[hoangzinh]

It seems the current behavior in Prod. Hmm, I think we can leave it as it is because it can be an expected behavior.

Screen.Recording.2024-12-04.at.18.04.13.mov

[FitseTLT]

Ok no problem 👍 @hoangzinh

[hoangzinh]

Reviewer Checklist

• I have verified the author checklist is complete (all boxes are checked off).
• I verified the correct issue is linked in the ### Fixed Issues section above
• I verified testing steps are clear and they cover the changes made in this PR
  • I verified the steps for local testing are in the Tests section
  • I verified the steps for Staging and/or Production testing are in the QA steps section
  • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
• I included screenshots or videos for tests on all platforms
• I verified tests pass on all platforms & I tested again on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
• If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
• I verified proper code patterns were followed (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
  • 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 verified that this PR follows the guidelines as stated in the Review Guidelines
• I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
• 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
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• 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.
• For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
• I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Screen.Recording.2024-12-09.at.22.36.52.android.mov

Android: mWeb Chrome

Screen.Recording.2024-12-09.at.22.48.56.android.chrome.mov

iOS: Native

Screen.Recording.2024-12-09.at.22.55.45.ios.mov

iOS: mWeb Safari

Screen.Recording.2024-12-09.at.23.04.46.ios.safari.mov

MacOS: Chrome / Safari

Screen.Recording.2024-12-09.at.22.13.11.web.mov

MacOS: Desktop

Screen.Recording.2024-12-09.at.22.21.20.desktop.mov

[hoangzinh]

@FitseTLT it seems the distance unit doesn't be reset if API is failed

Screen.Recording.2024-12-05.at.17.25.47.mov

[FitseTLT]

@FitseTLT it seems the distance unit doesn't be reset if API is failed

Screen.Recording.2024-12-05.at.17.25.47.mov

Fixed @hoangzinh

[hoangzinh]

Looks good @FitseTLT. I will try to complete checklist today

[hoangzinh]

BTW @hoangzinh simulate failing networks is not reliable. It makes the request fail immediately and the values will be reverted and error displayed but after a while it sends the request and the change will be pushed from the BE.

@FitseTLT, turn on both "Force offline" and "Simulate failing network requests" work to me. Wdyt if the testing steps here is:

1. Create a distance expense
2. Open the request details page
3. Open Testing preferences and turn on "Force offline" and "Simulate failing network requests"
4. Press on distance menu and change the waypoints by either adding a waypoint or dragging and reshuffling the waypoints
5. Click Save button
6. Open Testing preferences and turn off "Force offline"
7. Go to the request details page
8. Verify that after a while, it shows "Unexpected error editing this expense" and the waypoints are reverted to the previous value
9. Verify that there is a dismissable error shown below the map

[FitseTLT]

BTW @hoangzinh simulate failing networks is not reliable. It makes the request fail immediately and the values will be reverted and error displayed but after a while it sends the request and the change will be pushed from the BE.

@FitseTLT, turn on both "Force offline" and "Simulate failing network requests" work to me. Wdyt if the testing steps here is:

1. Create a distance expense
2. Open the request details page
3. Open Testing preferences and turn on "Force offline" and "Simulate failing network requests"
4. Press on distance menu and change the waypoints by either adding a waypoint or dragging and reshuffling the waypoints
5. Click Save button
6. Open Testing preferences and turn off "Force offline"
7. Go to the request details page
8. Verify that after a while, it shows "Unexpected error editing this expense" and the waypoints are reverted to the previous value
9. Verify that there is a dismissable error shown below the map

@hoangzinh The problem is after the data is reverted, error shown and so on, a bit later you will see the changes applied (even after clearing cache to prove that the BE request was really executed) by the way I have seen that our simulate failing network has the same problem in other requests too. So I am only worried that the QA would interpret this as the PR is failing.

[hoangzinh]

a bit later you will see the changes applied (even after clearing cache to prove that the BE request was really executed)

Hi @FitseTLT do you have any recordings/screenshots to illustrate what you mean here? I tried to reproduce it but I couldn't.

[FitseTLT]

a bit later you will see the changes applied (even after clearing cache to prove that the BE request was really executed)

Hi @FitseTLT do you have any recordings/screenshots to illustrate what you mean here? I tried to reproduce it but I couldn't.

Here it is @hoangzinh the request gets sent after the error occurred and values reverted when I turn off the simulate option
2024-12-10 16-20-29.mp4.zip
But because the request is sent after turning off the simulate failing ntwk option we can be good to go 👍

[hoangzinh]

we can be good to go 👍

@FitseTLT do you mean we can use those steps for QA steps?

[FitseTLT]

we can be good to go 👍

@FitseTLT do you mean we can use those steps for QA steps?

Yeah I think we shouldn't worry too much after all it not related with the current PR 👍

[hoangzinh]

Can you update it into QA steps? So they can test this PR on staging

[FitseTLT]

@hoangzinh Updated 👍

[FitseTLT]

@hoangzinh I think I have got better steps in #54023 ? Wouldn't it be better for QA steps. WDYT

[hoangzinh]

Looks good to me.

Screen.Recording.2024-12-12.at.22.19.54.mov

[FitseTLT]

Yep added it to the QA steps @pecanoro You can proceed with the review 👍

[pecanoro]

Small suggestion

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[github-actions]

🚀 Deployed to staging by https://github.com/pecanoro in version: 9.0.76-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	success ✅
🍎🔄 iOS HybridApp 🍎🔄	success ✅

[github-actions]

🚀 Deployed to production by https://github.com/grgia in version: 9.0.76-12 🚀

platform	result
🤖 android 🤖	true ❌
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	failure ❌
🍎🔄 iOS HybridApp 🍎🔄	success ✅