Skip to content

Handle raw Data type in iOS share extension for screenshot sharing#84387

Draft
MelvinBot wants to merge 1 commit intomainfrom
claude-fixShareExtensionScreenshotData
Draft

Handle raw Data type in iOS share extension for screenshot sharing#84387
MelvinBot wants to merge 1 commit intomainfrom
claude-fixShareExtensionScreenshotData

Conversation

@MelvinBot
Copy link
Contributor

@MelvinBot MelvinBot commented Mar 6, 2026

Explanation of Change

When sharing a screenshot directly from the iOS screenshot preview (the thumbnail that appears after taking a screenshot), iOS provides the image as raw Data bytes rather than an NSURL or UIImage. The share extension's handleData method in ShareViewController.swift was missing a case for this type, so the data silently fell through to the error handler. The app would still open (because openMainApp() is called regardless of errors in processAttachments) but no file was saved to the shared container, resulting in nothing happening.

This adds a Data handler that first attempts to decode the bytes as a UIImage (the common case for screenshots) and falls back to saving as a generic file for other data types.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/606736

Tests

  1. On iPhone, take a screenshot
  2. Tap the screenshot preview thumbnail in the bottom-left corner
  3. Tap "Share", then select "Expensify"
  4. Verify the "Share to Expensify" page appears and the image is loaded
  5. Also verify sharing from the Photos app still works as before (select an existing photo → Share → Expensify)
  • Verify that no errors appear in the JS console

Offline tests

N/A — the share extension operates on local data before opening the app.

QA Steps

  1. On iPhone, take a screenshot
  2. Tap the screenshot preview thumbnail in the bottom-left corner
  3. Tap "Share", then select "Expensify"
  4. Verify the "Share to Expensify" page appears and the image is loaded
  5. Also verify sharing from the Photos app still works as before (select an existing photo → Share → Expensify)
  • 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 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.
  • 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

N/A — iOS-only change

Android: mWeb Chrome

N/A — iOS-only change

iOS: Native

Requires manual testing on a physical iOS device with the share extension.

iOS: mWeb Safari

N/A — iOS-only change

MacOS: Chrome / Safari

N/A — iOS-only change

@MelvinBot @grgia
Handle raw Data type in iOS share extension for screenshot sharing
4326bf5 
When sharing a screenshot directly from the iOS screenshot preview,
iOS provides the image as raw Data bytes rather than a NSURL or UIImage.
The share extension's handleData method was missing a case for this type,
causing the data to silently fall through to the error handler. This meant
the app would open but no file was saved to the shared container.

Add a Data handler that first attempts to decode the bytes as a UIImage
(the common case for screenshots) and falls back to saving as a generic
file for other data types.

Co-authored-by: Georgia Monahan <grgia@users.noreply.github.com>
@MelvinBot MelvinBot requested a review from a team March 6, 2026 10:51
@github-actions
Copy link
Contributor

github-actions bot commented Mar 6, 2026

🚧 @grgia has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions
Copy link
Contributor

github-actions bot commented Mar 6, 2026

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #84387.

Android 🤖 iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-4326bf5-5430cbd-9eba66f84415d5769f4f6c4deadc0b5869c2bc16/index.html https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-4326bf5-5430cbd-40aca5860ad240782784277d27d7a632bce92337/index.html
Android iOS
Web 🕸️
https://84387.pr-testing.expensify.com
Web

👀 View the workflow run that generated this build 👀

@grgia
Copy link
Contributor

grgia commented Mar 6, 2026

@MelvinBot I tested this build on an IOS device and it does not fix the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@grgia grgia

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@MelvinBot @grgia