Report - Map disappears everytime user goes offline after changing expense rate.

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.52-2
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #97517
Email or phone of affected tester (no customers): ibellicotest+2766@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace.
Prerequisite 2: At least two distance rate created different from default one.

1. Open the staging.new.expensify.com website.
2. Open any workspace chat.
3. Create a map distance expense with a non default rate.
4. Navigate to "Workspace" > "Distance Rates"
5. Delete the just used rate.
6. Return to chat and open the just created expense.
7. Click on "Rate" field and edit the rate to a different non default one.
8. Return to chat.
9. Turn off internet connection.
10. Note that map disappears from expense preview.
11. Turn on internet connection again.
12. Note that map reappears.

Expected Result:

Map on distance expense should remain visible after going offline.

Actual Result:

Map on distance expense disappears everytime user goes offline if expense rate was previously edited.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7231186_1786472297492.Rate_Off.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7231186

Issue Owner

Current Issue Owner: @aimane-chnaif

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/60d7ddec94679c380bd8f4e48c42fe10ce49ecb7203fb4781cc11a073f3cc877

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #97517

[melvin-bot]

@Valforte @abdulrahuman5196 you have been assigned to this deploy blocker because you reviewed the offending PR: #97517

[melvin-bot]

@Gonals you have been assigned to this deploy blocker because you authored the offending PR: #97517

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.