Skip to content

[HOLD] [Odometer] Fix state restoration after App reload when image preview is open#82407

Draft
jakubkalinski0 wants to merge 2 commits intoExpensify:mainfrom
software-mansion-labs:jakubkalinski0/Odometer_Fix_navigation_after_App_reload_during_the_creation_flow_with_image_preview_open
Draft

[HOLD] [Odometer] Fix state restoration after App reload when image preview is open#82407
jakubkalinski0 wants to merge 2 commits intoExpensify:mainfrom
software-mansion-labs:jakubkalinski0/Odometer_Fix_navigation_after_App_reload_during_the_creation_flow_with_image_preview_open

Conversation

@jakubkalinski0
Copy link
Contributor

@jakubkalinski0 jakubkalinski0 commented Feb 13, 2026

Explanation of Change

ON HOLD -> There are more issues related to this that have to be taken care of and this is not a priority so I will be working on this PR from time to time and fix multitude of small issues here

Fixed Issues

$ #77266
PROPOSAL: N/A

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

  • 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
  • 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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • 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

codecov bot commented Feb 13, 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 Δ
...request/step/IOURequestStepOdometerImage/index.tsx 0.00% <ø> (ø)
...ou/request/step/IOURequestStepDistanceOdometer.tsx 0.00% <0.00%> (ø)
...libs/Navigation/helpers/getAdaptedStateFromPath.ts 40.87% <19.35%> (-7.31%) ⬇️
... and 38 files with indirect coverage changes

@jakubkalinski0 jakubkalinski0 changed the title [Odometer] Fixed navigation after App reload when image preview is open [On hold] [Odometer] Fixed navigation after App reload when image preview is open Feb 13, 2026
@jakubkalinski0 jakubkalinski0 changed the title [On hold] [Odometer] Fixed navigation after App reload when image preview is open [On hold] [Odometer] Fix state restoration after App reload when image preview is open Feb 13, 2026
@jakubkalinski0 jakubkalinski0 marked this pull request as ready for review February 13, 2026 15:26
@jakubkalinski0 jakubkalinski0 requested review from a team as code owners February 13, 2026 15:26
@melvin-bot melvin-bot bot requested review from a team, DylanDylann and heyjennahay and removed request for a team February 13, 2026 15:26
@melvin-bot
Copy link

melvin-bot bot commented Feb 13, 2026

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

@melvin-bot melvin-bot bot requested review from Julesssss and removed request for a team February 13, 2026 15:26
@melvin-bot
Copy link

melvin-bot bot commented Feb 13, 2026

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

@jakubkalinski0
Copy link
Contributor Author

Missclick - it's not ready for review yet

@jakubkalinski0 jakubkalinski0 marked this pull request as draft February 13, 2026 15:28
if (isEditingConfirmation) {
return;
}
if (!endImageSource?.startsWith('blob:')) {
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ PERF-12 (docs)

Missing cleanup for blob validation fetch

The validateOdometerBlobSource function initiates a fetch request but doesn't provide a cleanup mechanism. If the component unmounts while the fetch is in progress, the promise continues executing and may attempt to call removeMoneyRequestOdometerImage after unmount, potentially causing memory leaks or state updates on unmounted components.

Suggested fix:

const validateOdometerBlobSource = useCallback(
    (imageSource: string | undefined, imageType: OdometerImageType) => {
        if (\!imageSource?.startsWith('blob:')) {
            return;
        }

        const controller = new AbortController();
        
        fetch(imageSource, { signal: controller.signal })
            .catch((error) => {
                if (error.name === 'AbortError') {
                    return;
                }
                if (imageType === CONST.IOU.ODOMETER_IMAGE_TYPE.START) {
                    initialStartImageRef.current = undefined;
                } else {
                    initialEndImageRef.current = undefined;
                }
                removeMoneyRequestOdometerImage(transactionID, imageType, isTransactionDraft);
            });
        
        return controller;
    },
    [isTransactionDraft, transactionID],
);

useEffect(() => {
    const controller = validateOdometerBlobSource(startImageSource, CONST.IOU.ODOMETER_IMAGE_TYPE.START);
    return () => controller?.abort();
}, [startImageSource, validateOdometerBlobSource]);

useEffect(() => {
    const controller = validateOdometerBlobSource(endImageSource, CONST.IOU.ODOMETER_IMAGE_TYPE.END);
    return () => controller?.abort();
}, [endImageSource, validateOdometerBlobSource]);

Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

normalizedPath = '/';
}

if (normalizedPath.includes('/receipt/')) {
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ PERF-2 (docs)

Expensive work performed before validation

The code calls getStateFromPath(normalizedPath, options) before validating whether focusedRouteAsPartial meets all required conditions. If the route name check or parameter validation fails, the expensive state parsing was unnecessary.

Suggested fix:

Move the validation logic before calling getStateFromPath. Since you need the state to get the focused route, consider restructuring to avoid the second getStateFromPath call:

// First check if we need special handling
if (normalizedPath.includes('/receipt/')) {
    const stateWithOdometerReceiptPreview = getStateFromPath(normalizedPath, options) as PartialState<NavigationState<RootNavigatorParamList>>;
    const focusedRoute = stateWithOdometerReceiptPreview ? findFocusedRoute(stateWithOdometerReceiptPreview) : undefined;
    const focusedRouteAsPartial = focusedRoute as NavigationPartialRoute | undefined;

    if (focusedRouteAsPartial?.name === SCREENS.MONEY_REQUEST.RECEIPT_PREVIEW && isRouteWithOdometerReceiptPreviewParams(focusedRouteAsPartial)) {
        const {reportID} = focusedRouteAsPartial.params;
        if (isValidReportID(reportID)) {
            defaultFullScreenRouteSource = focusedRouteAsPartial;
            const {action, iouType, transactionID} = focusedRouteAsPartial.params;
            normalizedPath = `/${ROUTES.DISTANCE_REQUEST_CREATE_TAB_ODOMETER.getRoute(action, iouType, transactionID, reportID)}`;
        }
    }
}

const state = getStateFromPath(normalizedPath, options) as PartialState<NavigationState<RootNavigatorParamList>>;

Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.


const startImageSource = useMemo(() => getImageSource(odometerStartImage), [getImageSource, odometerStartImage]);
const endImageSource = useMemo(() => getImageSource(odometerEndImage), [getImageSource, odometerEndImage]);
const hasStartOdometerImage = !!startImageSource;
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ PERF-6 (docs)

Redundant state derived from memo

hasStartOdometerImage and hasEndOdometerImage are stored as constants but could be computed inline where used, or these are already derivable from startImageSource and endImageSource which are memoized.

Suggested fix:

Since these are only used once each in the handleOdometerImagePress calls, compute them inline:

onPress={() => {
    handleOdometerImagePress(CONST.IOU.ODOMETER_IMAGE_TYPE.START, !!startImageSource);
}}

// and

onPress={() => {
    handleOdometerImagePress(CONST.IOU.ODOMETER_IMAGE_TYPE.END, !!endImageSource);
}}

This eliminates the intermediate constants that don't add clarity.


Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Copy link

@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: 6d134646b2

ℹ️ 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".

const navigateBack = useCallback(() => {
Navigation.goBack(odometerRoute);
}, [odometerRoute]);
Navigation.goBack();

Choose a reason for hiding this comment

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

P2 Badge Restore explicit back target for odometer image screen

Using Navigation.goBack() without a fallback breaks the odometer flow when this screen is opened from a fresh URL state (for example after browser refresh or direct deep link): there may be no odometer route in history, so back navigation returns to an unrelated root screen (or cannot go back) instead of the odometer step. The previous goBack(ROUTES.DISTANCE_REQUEST_CREATE_TAB_ODOMETER...) behavior guaranteed users returned to the form after selecting/canceling an image.

Useful? React with 👍 / 👎.

@Julesssss Julesssss changed the title [On hold] [Odometer] Fix state restoration after App reload when image preview is open [HOLD] [Odometer] Fix state restoration after App reload when image preview is open Feb 23, 2026
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