chore(63871): update react-native-blob-util and expo-image #69649

Kureev · 2025-09-02T12:43:05Z

Explanation of Change

Update react-native-blob-util and expo-image versions to enable 16Kb memory pages (align=0x4000), which is required for Android 15+ compatibility.
armeabi-v7a libs remain at 4 KB alignment, which is expected since Android 15+ devices no longer run 32-bit code.

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

Fixed Issues

$ #63871
PROPOSAL: #63871

Tests

Ran llvm-readelf -l on all arm64-v8a .so files and confirmed p_align=0x4000 (16 KB) for each.
Verified that the APK/AAB passes zipalign -c -P 16.
Alternatively, run scripts/check-16kb-android.sh with the path to the APK to check all alignments in the bundle.
Installed the app on an Android 15 emulator and verified that it launches and runs without native crashes.
Confirmed no regressions in core flows (sign-in, navigation, chat, attachments).

Verify that no errors appear in the JS console

Offline tests

Tested launching the app with airplane mode enabled → verified it falls back gracefully (no native crashes).
Spotty connection simulation → verified chat messages queue and sync after reconnection.

QA Steps

Same as tests:

Confirm that the app installs and runs on Android 15 devices without native crashes.
Confirm normal behavior in core flows (login, messaging, navigation).
Verify that no errors appear in the JS console.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

melvin-bot · 2025-09-02T12:43:11Z

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

github-actions · 2025-09-02T12:43:15Z

⚠️ 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. ⚠️

jayeshmangwani · 2025-09-03T14:43:44Z

@Kureev expo-image fails to run on iOS.

Kureev · 2025-09-03T15:17:54Z

@jayeshmangwani when you teseted this, are you sure you pulled the correct submodule? https://github.com/Expensify/Mobile-Expensify/pull/13661

jayeshmangwani · 2025-09-03T15:27:48Z

@Kureev I tried this on a standalone app (not a hybrid app), so I’m not sure if it’s a submodule issue.

jayeshmangwani · 2025-09-05T05:57:27Z

@Kureev, please let me know if I need to do any additional setup to test this on iOS. I’ve pulled the PR, ran npm i and npm run pod-install, and then hit this error on iOS for the standalone app.

Kureev · 2025-09-05T08:15:54Z

yeah, I'm currently figuring this one out. Will keep you posted!

Kureev · 2025-09-05T10:36:07Z

fixed the build, @jayeshmangwani

Kureev · 2025-09-05T11:02:34Z

oh, seems there are some patches for the outdated versions of the expo packages. Will fix in a few mins

Kureev · 2025-09-05T11:18:28Z

tests seems to be flaky, locally they pass without issues.

will rebase on top of latest main and trigger them again

Kureev · 2025-09-05T11:23:27Z

some tests are failing, but I'm sure it is not related to this PR. Likely, someone updated the typescript version somewhere in the main branch

Kureev · 2025-09-05T13:56:26Z

@jayeshmangwani I think it is ready for review now. Should be all good with the builds

jayeshmangwani · 2025-09-05T15:36:34Z

Cool, I’m on the review now.

roryabraham · 2025-09-05T20:01:34Z

@Kureev tsc is failing

jayeshmangwani · 2025-09-07T12:49:04Z

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
- MacOS: Desktop
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 there are no new alerts related to the canBeMissing param for useOnyx
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 shown in the product is localized by adding it to src/languages/* files and using the translation method
- 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 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)
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
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.
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.
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

Android: HybridApp

Android.mp4

Android: mWeb Chrome

mweb-chrome.mov

iOS: HybridApp

iOS.mov

iOS: mWeb Safari

mweb-safari.mov

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

desktop.mov

jayeshmangwani · 2025-09-07T12:53:00Z

@Kureev typecheck is failing on this PR only because of the line "moduleResolution": "node" in tsconfig.json.

On the main, typecheck passes.

Kureev · 2025-09-08T09:05:15Z

@jayeshmangwani rebased on top of the main, let's keep an eye on the tests, hopefully everything pass now

jayeshmangwani · 2025-09-08T09:19:04Z

@Kureev This issue might be due to the updated expo-image version, since it’s only failing on our PR. You can verify by runningnpm run typecheck locally.

This reverts commit 93dc226.

Kureev · 2025-09-14T14:52:59Z

Okay, it seems the problem was in the main branch and not related to this PR (after merging main it went away). Ready for review/merge

jayeshmangwani · 2025-09-15T18:30:11Z

@Kureev , I don’t think we want to commit the Mobile-Expensify changes in this PR.

Kureev · 2025-09-15T19:18:20Z

ah right, probably slipped in one of the merges. Let me fix this real quick

Kureev · 2025-09-15T19:20:55Z

@jayeshmangwani reverted submodule to the current main

jayeshmangwani

PR works well, lgtm 🚀

roryabraham · 2025-09-15T21:26:32Z

Do we have a Mobile-Expensify counterpart for this PR?

Kureev · 2025-09-15T21:27:55Z

@roryabraham not this one

roryabraham · 2025-09-15T21:30:44Z

Reassure is failing everywhere, going to ignore it for now. slack context: https://expensify.slack.com/archives/C01GTK53T8Q/p1757971409580299?thread_ts=1757006279.943369&cid=C01GTK53T8Q

OSBotify · 2025-09-15T21:41:54Z

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

OSBotify · 2025-09-16T18:31:58Z

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

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

roryabraham · 2025-09-16T20:52:00Z

The TSConfig changes made to scripts/tsconfig.json are causing all sorts of problems for me while working on scripts. I still don't really understand how updating react-native-blob-util and expo-image necessitated tsconfig changes to .github/tsconfig.json and scripts/tsconfig.json

Kureev · 2025-09-17T14:49:49Z

The TSConfig changes made to scripts/tsconfig.json are causing all sorts of problems for me while working on scripts. I still don't really understand how updating react-native-blob-util and expo-image necessitated tsconfig changes to .github/tsconfig.json and scripts/tsconfig.json

see #69649 (comment)

…part4" This reverts commit 8ddfa01, reversing changes made to 262cf37.

[CP Staging] Revert "Merge pull request #69649 from margelo/kureev/63871-part4"

[CP Staging] Revert "Merge pull request #69649 from margelo/kureev/63871-part4" (cherry picked from commit aaa84b9) (cherry-picked to staging by Beamanator)

OSBotify · 2025-09-19T22:23:11Z

🚀 Deployed to production by https://github.com/Beamanator in version: 9.2.15-15 🚀

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

OSBotify · 2025-09-19T22:51:45Z

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

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	failure ❌

OSBotify · 2025-09-23T19:33:58Z

🚀 Deployed to production by https://github.com/roryabraham in version: 9.2.16-14 🚀

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

Kureev requested a review from a team as a code owner September 2, 2025 12:43

melvin-bot bot assigned Kureev Sep 2, 2025

melvin-bot bot requested review from jayeshmangwani and removed request for a team September 2, 2025 12:43

Kureev mentioned this pull request Sep 2, 2025

[HOLD] Enable 16KB memory page size on Android #69161

Closed

51 tasks

roryabraham self-requested a review September 3, 2025 05:13

Kureev force-pushed the kureev/63871-part4 branch from 3175cb5 to 077de80 Compare September 5, 2025 10:35

Kureev force-pushed the kureev/63871-part4 branch from 49faea3 to e45240e Compare September 5, 2025 11:19

Kureev force-pushed the kureev/63871-part4 branch from e45240e to f2f1285 Compare September 5, 2025 13:41

roryabraham mentioned this pull request Sep 5, 2025

[HOLD https://github.com/callstackincubator/android/issues/15] [$250] Enable 16KB memory page size on Android #63871

Open

Kureev force-pushed the kureev/63871-part4 branch from f2f1285 to 1e5a547 Compare September 8, 2025 09:04

Kureev force-pushed the kureev/63871-part4 branch from b41bd39 to c79e654 Compare September 8, 2025 14:04

Kureev added 3 commits September 14, 2025 13:42

chore(63871): merge in main

93dc226

Revert "chore(63871): merge in main"

298a904

This reverts commit 93dc226.

fix(63871): attempt to build with original submodule

a05b689

Kureev requested a review from roryabraham September 14, 2025 14:53

Kureev added 2 commits September 15, 2025 15:04

Merge branch 'main' into kureev/63871-part4

ff11a61

Merge branch 'main' into kureev/63871-part4

aeb4c46

fix(63871): revert submodule to the version from main

3283233

Merge branch 'main' into kureev/63871-part4

c609e8f

jayeshmangwani approved these changes Sep 15, 2025

View reviewed changes

roryabraham approved these changes Sep 15, 2025

View reviewed changes

roryabraham merged commit 8ddfa01 into Expensify:main Sep 15, 2025
29 of 30 checks passed

OSBotify mentioned this pull request Sep 16, 2025

Deploy Checklist: New Expensify 2025-09-16 #70674

Closed

91 tasks

Kureev added a commit to margelo/Expensify that referenced this pull request Sep 17, 2025

Revert "Merge pull request Expensify#69649 from margelo/kureev/63871-…

089c6cc

…part4" This reverts commit 8ddfa01, reversing changes made to 262cf37.

mountiny added a commit that referenced this pull request Sep 17, 2025

Merge pull request #70754 from margelo/kureev/revert-expo-image-update

aaa84b9

[CP Staging] Revert "Merge pull request #69649 from margelo/kureev/63871-part4"

Kureev mentioned this pull request Sep 18, 2025

fix(63871): expo-image update #70795

Closed

51 tasks

chore(63871): update react-native-blob-util and expo-image #69649

chore(63871): update react-native-blob-util and expo-image #69649

Uh oh!

Conversation

Kureev commented Sep 2, 2025

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Sep 2, 2025

Uh oh!

github-actions bot commented Sep 2, 2025

Uh oh!

jayeshmangwani commented Sep 3, 2025

Uh oh!

Kureev commented Sep 3, 2025

Uh oh!

jayeshmangwani commented Sep 3, 2025

Uh oh!

jayeshmangwani commented Sep 5, 2025

Uh oh!

Kureev commented Sep 5, 2025

Uh oh!

Kureev commented Sep 5, 2025

Uh oh!

Kureev commented Sep 5, 2025

Uh oh!

Kureev commented Sep 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Kureev commented Sep 5, 2025

Uh oh!

Kureev commented Sep 5, 2025

Uh oh!

jayeshmangwani commented Sep 5, 2025

Uh oh!

roryabraham commented Sep 5, 2025

Uh oh!

jayeshmangwani commented Sep 7, 2025

Reviewer Checklist

Screenshots/Videos

Uh oh!

jayeshmangwani commented Sep 7, 2025

Uh oh!

Kureev commented Sep 8, 2025

Uh oh!

jayeshmangwani commented Sep 8, 2025

Uh oh!

Kureev commented Sep 14, 2025

Uh oh!

jayeshmangwani commented Sep 15, 2025

Uh oh!

Kureev commented Sep 15, 2025

Uh oh!

Kureev commented Sep 15, 2025

Uh oh!

jayeshmangwani left a comment

Choose a reason for hiding this comment

Uh oh!

roryabraham commented Sep 15, 2025

Uh oh!

Kureev commented Sep 15, 2025

Uh oh!

roryabraham commented Sep 15, 2025

Uh oh!

Uh oh!

OSBotify commented Sep 15, 2025

Uh oh!

OSBotify commented Sep 16, 2025

Uh oh!

roryabraham commented Sep 16, 2025

Uh oh!

Kureev commented Sep 17, 2025

Uh oh!

OSBotify commented Sep 19, 2025

Uh oh!

Kureev commented Sep 5, 2025 •

edited

Loading