Skip to content

Bump @react-native-documents/picker to 12.0.3 - #106481

Merged
roryabraham merged 2 commits into
Expensify:mainfrom
software-mansion-labs:collectioneur/bump-documents-picker
Nov 14, 2026
Merged

roryabraham merged 2 commits into
Expensify:mainfrom
software-mansion-labs:collectioneur/bump-documents-picker

Conversation

@collectioneur

@collectioneur collectioneur commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Upgrades @react-native-documents/picker from 10.1.3 to 12.0.3.

This is one of the dependency bumps split out of the React Native 0.88 upgrade (#101739), so it can be tested and shipped on the current React Native 0.86 before the upgrade lands. On Android, 12.x reads the activity through reactApplicationContext.currentActivity in pick, saveDocument and pickDirectory.

Upstream changes between 10.1.3 and 12.0.3 include:

  • 11.0.0: the package ships ES modules only (no CommonJS build). Re.Pack bundles it as is, and Jest keeps using __mocks__/@react-native-documents/picker.ts.
  • 11.0.2: every rejection goes through the same promise wrapper. Cancelling still rejects with the OPERATION_CANCELED code, so our checks in AttachmentPicker and FilePicker still treat it as a cancel (covered by tests 2 and 4).
  • 11.0.3 / 11.0.4: Android no longer uses the deprecated currentActivity getter, and coroutine cancellation no longer leaves promises hanging.
  • 12.0.0: the iOS module moves to Swift 6 concurrency, and Android handles errors when it reads file metadata.
  • 12.0.1 - 12.0.3: Jest setup warnings, podspec source URLs, and Android builds where AGP 9 registers Kotlin itself.

The library is only imported from src/components/AttachmentPicker/index.native.tsx and src/components/FilePicker/index.native.tsx. The web versions of both components use <input type="file">, and the web build does not resolve .native.* files, so web and mWeb are not affected.

This PR updates the react-native-document-picker pod version and checksum in ios/Podfile.lock (standalone NewDot), and the Mobile-Expensify PR does the same in its Podfile.lock (HybridApp).

Fixed Issues

$ #106112
PROPOSAL: N/A

MOBILE-EXPENSIFY: https://github.com/Expensify/Mobile-Expensify/pull/14222

Tests

@react-native-documents/picker is only used on native, so these steps are for the HybridApp on iOS and Android. Web and mWeb are N/A.

Test 1: Attach a single file in a chat

  1. Open any chat and tap + > Add attachment > Choose file.
  2. Verify the system file picker opens.
  3. Pick one file (for example a .txt). On iOS tap the file and then Open. On Android tap the file.
  4. Verify the file is sent to the chat as an attachment.

Test 2: Cancel the picker in a chat

  1. Open any chat and tap + > Add attachment > Choose file.
  2. Close the picker without picking a file. On iOS tap the close (✕) button. On Android press the system Back button.
  3. Verify the picker closes, you stay in the chat, and no error alert appears.

Test 3: Attach several files at once in a chat

  1. Open any chat and tap + > Add attachment > Choose file.
  2. Select a PDF and a second file. On iOS tap both files and then Open. On Android long-press the first file, tap the second one, and tap Select.
  3. Verify both files are sent to the chat and the PDF shows a preview.

Test 4: Cancel the picker in Import spreadsheet

  1. Go to Workspaces > a workspace you own > Categories > More > Import spreadsheet.
  2. Tap Choose file, then close the picker without picking a file (iOS: close button, Android: system Back).
  3. Verify the picker closes, you stay on Import spreadsheet, and no error alert appears.

Test 5: Pick a CSV in Import spreadsheet

  1. Prepare a CSV with a header row, for example:
    Category,Enabled
    Picker Test Category,true
    
  2. Go to Workspaces > a workspace you own > Categories > More > Import spreadsheet and tap Choose file.
  3. Pick the CSV.
  4. Verify the Import categories screen opens and shows the Category and Enabled columns with the values from the file. You don't need to tap Import.

Offline tests

N/A. The picker only reads files on the device, and offline handling of the resulting upload is unchanged by this bump.

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 verified any copy / text that was added to the app 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 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 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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

Test 1:

1-attachment-single-file.mp4

Test 2:

2-attachment-cancel.mp4

Test 3:

3-attachment-multi-select-pdf-txt.mp4

Test 4:

4-file-picker-cancel.mp4

Test 5:

5-file-picker-csv-import.mp4
Android: mWeb Chrome

N/A. The library is native-only, web uses <input type="file">.

iOS: Native

Test 1:

1-attachment-single-file.mp4

Test 2:

2-attachment-cancel.mp4

Test 3:

3-attachment-multi-select-pdf-txt.mp4

Test 4:

4-file-picker-cancel.mp4

Test 5:

5-file-picker-csv-import.mp4
iOS: mWeb Safari

N/A. The library is native-only, web uses <input type="file">.

MacOS: Chrome / Safari

N/A. The library is native-only, web uses <input type="file">.

@github-actions

Copy link
Copy Markdown
Contributor

⚠️ This PR is possibly changing native code and/or updating libraries, it may cause problems with HybridApp. Please check if any patch updates are required in the HybridApp repo and run an AdHoc build to verify that HybridApp will not break. Ask Contributor Plus for help if you are not sure how to handle this. ⚠️

@collectioneur
collectioneur force-pushed the collectioneur/bump-documents-picker branch from 0f57183 to 15ef734 Compare November 10, 2026 11:35
@collectioneur
collectioneur marked this pull request as ready for review November 10, 2026 12:57
@collectioneur
collectioneur requested a review from a team as a code owner November 10, 2026 12:57
@melvin-bot
melvin-bot Bot requested review from gijoe0295 and removed request for a team November 10, 2026 12:57
@melvin-bot

melvin-bot Bot commented Nov 10, 2026

Copy link
Copy Markdown

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

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-10T13:11:41.411072Z 15ef734 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@github-actions

Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

@mountiny
mountiny requested review from shubham1206agra and removed request for gijoe0295 November 10, 2026 19:00
@collectioneur

Copy link
Copy Markdown
Contributor Author

@shubham1206agra could you please review this PR?

@mountiny

Copy link
Copy Markdown
Contributor

@shubham1206agra bumpity bump

@shubham1206agra

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (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 verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • 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 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.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

WhatsApp.Video.2026-11-14.at.18.07.16.mp4
ScreenRecording_11-14-2026.08-38-11_1.MP4

@melvin-bot
melvin-bot Bot requested review from mountiny and roryabraham November 14, 2026 12:39
@roryabraham
roryabraham merged commit 222423b into Expensify:main Nov 14, 2026
44 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@github-actions

Copy link
Copy Markdown
Contributor

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/roryabraham in version: 9.5.40-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

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.

5 participants