Skip to content

Save unsent receipts to the device gallery on sign-out (native)#94327

Closed
adhorodyski wants to merge 4 commits into
Expensify:mainfrom
callstack-internal:durable-receipts-save-signout
Closed

Save unsent receipts to the device gallery on sign-out (native)#94327
adhorodyski wants to merge 4 commits into
Expensify:mainfrom
callstack-internal:durable-receipts-save-signout

Conversation

@adhorodyski

@adhorodyski adhorodyski commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

On iOS and Android, if you sign out while a receipt is still uploading, the app now saves that receipt image to your device gallery before it clears storage. That way you can add it again later instead of losing it.

Manual sign-out from Settings shows a short confirmation prompt. Forced sign-outs (expired or invalid session) save silently without a prompt. If saving fails for any reason, sign-out still completes normally.

Fixed Issues

$ #92139
PROPOSAL:

Tests

Unit tests (all passing):

  • Pending-receipt enumeration (savePendingReceiptsToGalleryTest.ts): verifies correct receipts are picked from the Onyx queue
  • Gallery-save batch behavior: one write per file, survives a single failure, swallows errors so sign-out always completes
  • SignInRedirectSaveReceiptsTest.ts: verifies save-before-clear ordering and the fail-safe (sign-out completes even if saving throws)

Manual tests still to be done on real devices (not yet verified — marking in QA steps):

  • Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

iOS Native and Android Native only (web behavior is unchanged).

  1. Capture a receipt while the device is offline so it stays in the upload queue.
  2. Go to Settings and tap Sign Out.
  3. Verify a confirmation prompt appears mentioning unsaved receipts.
  4. Confirm sign-out. Verify the receipt image appears in the device gallery and sign-out completes.
  5. Repeat step 1. Trigger a forced sign-out (e.g. invalidate the session from another device). Verify the receipt is saved to the gallery with no prompt shown and sign-out completes.
  6. Repeat step 1. Deny photo-library permission when prompted (or pre-deny it in Settings). Tap Sign Out and confirm. Verify sign-out still completes even though the gallery save fails.
  7. iOS-specific: Verify the image lands in the Camera Roll via the Photos framework.
  8. Android-specific: Verify the image lands in the media store (visible in the Gallery app).
  • 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 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 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)
  • 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)
  • 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.
  • 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

@melvin-bot

melvin-bot Bot commented Jun 23, 2026

Copy link
Copy Markdown

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@codecov

codecov Bot commented Jun 23, 2026

Copy link
Copy Markdown

@adhorodyski

Copy link
Copy Markdown
Contributor Author

@codex review

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

Copy link
Copy Markdown

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: a5e4dd912f

ℹ️ 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/savePendingReceiptsToGallery/getPendingReceiptRequests.ts
Comment thread src/libs/savePendingReceiptsToGallery/getPendingReceiptRequests.ts Outdated
adhorodyski and others added 2 commits June 24, 2026 14:23
…ut save

getPendingReceiptRequests() missed pending receipts in two ways, both of which
let Onyx.clear() delete a local receipt on sign-out without saving it:

- REPLACE_RECEIPT queues the raw File object, whose local path lives under `uri`
  (and name under `name`), not `source`/`localSource`. It was allow-listed but
  could never match, so every offline receipt-replace was silently dropped.
  Fall back to `uri` for the path and `name` for the filename.
- Other receipt-bearing commands (SEND_MONEY_ELSEWHERE, SEND_MONEY_WITH_WALLET,
  SHARE_TRACKED_EXPENSE, CATEGORIZE_TRACKED_EXPENSE, ADD_TRACKED_EXPENSE_TO_POLICY)
  were absent from the allow-list. Add them.

Also collapse the repeated string-property guards into a single isRecord-based
getString helper.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@adhorodyski

Copy link
Copy Markdown
Contributor Author

Closing as well, there's another copy by @rinej

@adhorodyski adhorodyski closed this Jul 3, 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