Skip to content

[Odometer] Add save for later functionality#87726

Draft
jakubkalinski0 wants to merge 21 commits intoExpensify:mainfrom
software-mansion-labs:jakubkalinski0/Odometer_add_save_for_later_functionality
Draft

[Odometer] Add save for later functionality#87726
jakubkalinski0 wants to merge 21 commits intoExpensify:mainfrom
software-mansion-labs:jakubkalinski0/Odometer_add_save_for_later_functionality

Conversation

@jakubkalinski0
Copy link
Copy Markdown
Contributor

@jakubkalinski0 jakubkalinski0 commented Apr 12, 2026

Explanation of Change

Adds "Save for later" functionality to the Odometer screen for new distance requests. A new ODOMETER_DRAFT Onyx key persists start/end readings and images (base64 on web, URI on native). When the user returns to the Odometer tab, the draft is hydrated back into the transaction. Draft is cleared on successful submission.

Important

Screenshots from the Design Doc for more context

Add Save for later button to the Odometer expense page (Issue #87817) image
Add ability for Odometer readings and image data to be saved to device storage (Issue #87818) image
Modify Odometer expense tab to detect and retrieve draft expense data (Issue #87819) image
Details image

Fixed Issues

$ #87817
$ #87818
$ #87819
PROPOSAL: N/A

Tests

  1. Open the app and start creating a new distance (odometer) expense request.
  2. Navigate to the Odometer tab, enter a start and end readings, attach at least 1 odometer image.
  3. Tap "Save for later" and verify if the RHP is closed properly.
  4. Return to the Odometer tab verify the previously entered readings and images are restored automatically.

  1. Start a new odometer distance request with no data entered (empty readings, no images) - you can just clear the values/images manually or log out and log in.
  2. Tap "Save for later".
  3. Verify no draft is persisted (verify that Onyx odometerDraft key is null using DevTools) and you navigate back normally, i.e. RHP is closed properly.

  1. Start a new odometer distance request, enter readings and images.
  2. Tap "Save for later".
  3. Create another type of expense.
  4. Return to Odometer tab and verify that the odometerDraft data is still there.

  1. Start a new odometer request, enter readings and images, then tap "Save for later".
  2. Return to Odometer tab and complete the expense submission (tap "Next" -> "Create").
  3. Verify the expense is created properly and that odometerDraft Onyx key is cleared after successful submission.

  1. Start a new odometer request, enter readings and images, then tap "Save for later".
  2. Close the App.
  3. (You can wait as long as you wish between sessions - as long as you do not log out the odometerDraft Onyx key should still hold this info - on the same platform ofc).
  4. Open the App once again.
  5. Return to Odometer tab and complete the expense submission (tap "Next" -> "Create").
  6. Verify the expense is created properly and that odometerDraft Onyx key is cleared after successful submission.

Offline tests

Same as Tests (with the difference that when you tap "Create" the expense will be pending until you go back Online)

QA Steps

Same as Tests

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
  • 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 new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • 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: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 12, 2026

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/CONST/index.ts 92.30% <ø> (ø)
src/ONYXKEYS.ts 100.00% <ø> (ø)
src/hooks/useResetIOUType.ts 100.00% <100.00%> (ø)
src/libs/actions/IOU/TrackExpense.ts 80.03% <50.00%> (-0.11%) ⬇️
src/libs/fileDownload/FileUtils.ts 30.58% <0.00%> (-2.23%) ⬇️
...ou/request/step/IOURequestStepDistanceOdometer.tsx 0.00% <0.00%> (ø)
src/libs/actions/IOU/index.ts 78.83% <3.44%> (-4.24%) ⬇️
... and 33 files with indirect coverage changes

…unctionality

# Conflicts:
#	Mobile-Expensify
#	android/app/build.gradle
#	ios/NewExpensify/Info.plist
#	ios/NotificationServiceExtension/Info.plist
#	ios/ShareViewController/Info.plist
#	package-lock.json
#	package.json
#	src/CONST/index.ts
#	src/ROUTES.ts
#	src/SCREENS.ts
#	src/components/ReportActionItem/MoneyRequestReportPreview/MoneyRequestReportPreviewContent.tsx
#	src/components/TransactionItemRow/index.tsx
#	src/languages/de.ts
#	src/languages/en.ts
#	src/languages/es.ts
#	src/languages/fr.ts
#	src/languages/it.ts
#	src/languages/ja.ts
#	src/languages/nl.ts
#	src/languages/pl.ts
#	src/languages/pt-BR.ts
#	src/languages/zh-hans.ts
#	src/libs/Navigation/AppNavigator/ModalStackNavigators/index.tsx
#	src/libs/Navigation/linkingConfig/OldRoutes.ts
#	src/libs/Navigation/linkingConfig/RELATIONS/WORKSPACE_TO_RHP.ts
#	src/libs/Navigation/linkingConfig/config.ts
#	src/libs/Navigation/types.ts
#	src/libs/ReportUtils.ts
#	src/libs/actions/IOU/index.ts
#	src/libs/actions/connections/NetSuiteCommands.ts
#	src/pages/inbox/report/PureReportActionItem.tsx
#	src/pages/inbox/report/ReportActionItem.tsx
#	src/pages/iou/request/step/IOURequestStepConfirmation.tsx
#	src/pages/workspace/accounting/intacct/export/DynamicSageIntacctNonReimbursableExpensesDestinationPage.tsx
#	src/pages/workspace/accounting/intacct/export/SageIntacctExportPage.tsx
#	src/pages/workspace/companyCards/WorkspaceCompanyCardExpensifyCardPromotionBanner.tsx
#	src/types/onyx/Policy.ts
#	tests/actions/connections/NetSuite.ts
#	tests/navigation/getMatchingNewRouteTest.ts
#	tests/unit/ReportActionsUtilsTest.ts
…ardConfirmationRef to match new implementation
@jakubkalinski0
Copy link
Copy Markdown
Contributor Author

@codex review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4fbd413f8f

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/libs/actions/IOU/index.ts
@jakubkalinski0
Copy link
Copy Markdown
Contributor Author

@codex review pls

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ddb1c9223e

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/libs/actions/IOU/index.ts
@jakubkalinski0
Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector
Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Keep it up!

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

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.

1 participant