Skip to content

Match Metro's Android release assets in Re.Pack - #102766

Merged
roryabraham merged 8 commits into
Expensify:mainfrom
callstack-internal:eliran/repack-android-fonts-raw
Oct 14, 2026
Merged

roryabraham merged 8 commits into
Expensify:mainfrom
callstack-internal:eliran/repack-android-fonts-raw

Conversation

@elirangoshen

@elirangoshen elirangoshen commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Re.Pack's Android release asset output differs from Metro's in two ways. Both break HybridApp Android release builds bundled with Re.Pack:

  1. Fonts go to res/font/ instead of res/raw/ (@callstack+repack+5.3.0+003+android-fonts-raw.patch). Skia's useFont resolves require()d fonts with getIdentifier(name, "drawable") and then "raw", and never looks in font. The Home "Spend over time" chart fonts never loaded, so the chart spun forever. The patch sends .ttf/.otf/.ttc files to raw, as Metro does. XML font-family resources still go to font/.
  2. No res/raw/keep.xml (@callstack+repack+5.3.0+004+android-keep-xml.patch). Metro writes a tools:keep list of every bundled resource, because JS loads them by name and the resource shrinker can't see that. Without it, builds with shrinkResources (standalone Android release) can strip images and fonts that are still used. The patch writes the same file from Re.Pack's assets copy step.

With both patches, an Android release bundle from Re.Pack matches Metro's: the same 13 font files in raw/, and the same 787 keep.xml entries (Metro also lists 5 LogBox images that only exist in dev).

Fixed Issues

$ #100202

Tests

  1. Run npm ci and confirm patch-package applies all four @callstack/repack patches (001 to 004) with no errors.
  2. Bundle Android release with Re.Pack:
    npx rock bundle --platform android --dev false --entry-file index.js --bundle-output /tmp/repack/index.android.bundle --assets-dest /tmp/repack/res
  3. Verify there's no /tmp/repack/res/font/ folder, and that the .otf font files (e.g. assets_fonts_native_expensifyneueregular.otf) are in /tmp/repack/res/raw/.
  4. Verify /tmp/repack/res/raw/keep.xml exists and lists @drawable/... and @raw/... entries.
  5. Optional, to compare with Metro: run step 2 again with BUNDLER=metro into /tmp/metro. diff -rq /tmp/metro/res /tmp/repack/res should only show the 5 LogBox drawables plus a different keep.xml, and the two keep.xml files should differ only by those 5 entries.
  6. Build an Android HybridApp release APK bundled with Re.Pack: in Mobile-Expensify/Android/build.gradle, set cliFile = file("$newDotNodeModules/rock/dist/src/bin.js") and bundleCommand = "bundle" in the react { } block, then run ./gradlew assembleRelease from Mobile-Expensify/Android and install the APK.
  7. Do the QA steps below on that APK.
  • Verify that no errors appear in the JS console

Offline tests

N/A. This only changes where bundled assets are written at build time.

QA Steps

Android only. Use a workspace you own, and turn on Tags and Per diem in More features.

  1. Open Home, scroll to "Spend over time", and verify the chart loads with its axis labels.
  2. Workspace > Tags > More > Import spreadsheet > Multi-level tags. Choose a CSV with a header row and three columns (e.g. State,Region,Team), turn on "These are independent tags", tap Next, then Import. Verify "Import successful" appears and the tag lists show up.
  3. Workspace > Per diem > Import spreadsheet. Choose a CSV with Destination,Subrate,Amount,Currency columns and tap Import. Verify "Import successful" appears and the rates are listed.
  4. Workspace > Categories > More > Import spreadsheet. Map the name column to "Name" and tap Import. Verify "Import successful" appears and the categories are listed.
  5. Workspace > Members > More > Import spreadsheet. Choose a CSV with an Email column and tap Import. Verify "Import successful" appears and the members are listed.
  6. In the workspace chat, tap + > Create expense > Scan > gallery > Choose file, pick an image, and create the expense. Verify it's created with the receipt.
  • 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 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 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 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 0-home-chart 3-tags-success 6-perdiem-success
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

Re.Pack puts Android fonts in res/font, where Skia's useFont never looks,
so Home charts never loaded in HybridApp release builds (Expensify#102619). It also
writes no raw/keep.xml, so shrinkResources can strip bundled assets.
Patch both to match Metro: fonts go to raw/, and keep.xml lists every
bundled resource.
@github-actions

github-actions Bot commented Oct 1, 2026

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

@elirangoshen
elirangoshen marked this pull request as ready for review October 1, 2026 13:14
@elirangoshen
elirangoshen requested a review from a team as a code owner October 1, 2026 13:14
@melvin-bot
melvin-bot Bot requested review from rojiphil and removed request for a team October 1, 2026 13:14
@melvin-bot

melvin-bot Bot commented Oct 1, 2026

Copy link
Copy Markdown

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

@elirangoshen

Copy link
Copy Markdown
Contributor Author

Hi, will there be any update ? @rojiphil

@rojiphil

rojiphil commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

@elirangoshen Sorry for the delayed response here. Will share review update in few hours.

@elirangoshen

Copy link
Copy Markdown
Contributor Author

@elirangoshen Sorry for the delayed response here. Will share review update in few hours.

Sure thanks

@mountiny
mountiny requested review from roryabraham and removed request for rojiphil October 2, 2026 13:10
@mountiny

mountiny commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Does this require C+ review? looks like the original PR did not have a c+ review

@rojiphil

rojiphil commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Ok. Nevertheless, sharing one observation related to importing tags.

@elirangoshen The production release version was able to import the tags but the apk built via this pr was not able to. Whereas it was possible to import categories, per-diem and members
Is this due to the changes here?

expensify-pr.mp4
expensify-production.mp4

@elirangoshen

Copy link
Copy Markdown
Contributor Author

Ok. Nevertheless, sharing one observation related to importing tags.

@elirangoshen The production release version was able to import the tags but the apk built via this pr was not able to. Whereas it was possible to import categories, per-diem and members

Is this due to the changes here?

expensify-pr.mp4
expensify-production.mp4

Thanks for the update I will look into it and update.

@elirangoshen

elirangoshen commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor Author

Ok. Nevertheless, sharing one observation related to importing tags.

@elirangoshen The production release version was able to import the tags but the apk built via this pr was not able to. Whereas it was possible to import categories, per-diem and members Is this due to the changes here?

expensify-pr.mp4
expensify-production.mp4

this issue #102623 is related but closed due to the revert. I will check when they wan to reopen this one. this pr suppose to fix it
#102681

So the bug you find belong to to other issue, i will try to re-open the other one.

@elirangoshen

Copy link
Copy Markdown
Contributor Author

As mention earlier, there's already upstream fix in their repo. so it might of matter of days until it will be published.

Should we patch it anyway until it will be merged so we wont delay until (or just point our repack repo at the commit) ? @mountiny @rojiphil

@mountiny

mountiny commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

I think we can patch and then remove it once the version is released its easy

@mountiny

mountiny commented Oct 5, 2026

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 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
    • 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
    • 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 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 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).
  • 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: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari

mountiny
mountiny previously approved these changes Oct 5, 2026

@mountiny mountiny left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@MelvinBot can you create Weekly Task issue and assign @mountiny @elirangoshen that will be tracking to remove the patch and update the library version?

@mountiny mountiny changed the title Match Metro's Android release assets in Re.Pack [HOLD https://github.com/Expensify/App/pull/102681] Match Metro's Android release assets in Re.Pack Oct 5, 2026
@MelvinBot

Copy link
Copy Markdown
Contributor

I created [DX] Remove Re.Pack Android assets patches and update @callstack/repack. It has the Weekly and Task labels, and mountiny and elirangoshen are assigned.

The issue tracks two steps for when Re.Pack publishes the upstream fix (callstack/repack#1472, closed on 2026-10-02 but not released yet):

  1. Remove the 003 and 004 patches.
  2. Update @callstack/repack.

It also includes the steps to verify the change.


view run

@roryabraham

roryabraham commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

Let's use an AdHoc build to test a "canary" as requested in the upstream issue: callstack/repack#1472 (comment)

@github-actions

github-actions Bot commented Oct 5, 2026

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.

@kacper-mikolajczak

kacper-mikolajczak commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

The Re.pack v5.4.1 is out 🎉 The PR was updated to accommodate for that.

Could I ask you to please re-run the test 7 job? I think it should be fine after merging latest main 🙏

Apart from above, we should be good to go 🚀

CC @elirangoshen @mountiny @roryabraham

@kacper-mikolajczak

Copy link
Copy Markdown
Contributor

Hmm, weird that the tests are failing on this type of changes. @mountiny could we re-run the 4th suite, please 🙏

@mountiny

Copy link
Copy Markdown
Contributor

re-ran

@kacper-mikolajczak

Copy link
Copy Markdown
Contributor

Looks like it's OK now. The PR is ready to be merged

@elirangoshen elirangoshen changed the title [HOLD https://github.com/Expensify/App/pull/102681] Match Metro's Android release assets in Re.Pack Match Metro's Android release assets in Re.Pack Oct 13, 2026
@elirangoshen
elirangoshen requested a review from mountiny October 13, 2026 09:42
@github-actions

Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

@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-10-13.at.21.52.54.mp4

@elirangoshen

Copy link
Copy Markdown
Contributor Author

thanks @shubham1206agra I hope it will be merged today as there's other pr's that depends on this one :)

@shubham1206agra

Copy link
Copy Markdown
Contributor

@mountiny is OOO today. So, not sure it will be merged today.

@roryabraham
roryabraham merged commit 1aae33a into Expensify:main Oct 14, 2026
52 of 55 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.

@elirangoshen elirangoshen mentioned this pull request Oct 15, 2026
38 tasks done
@OSBotify

Copy link
Copy Markdown
Contributor

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

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

@OSBotify

Copy link
Copy Markdown
Contributor

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

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/cristipaval in version: 9.5.12-1 🚀

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

Bundle Size Analysis (Sentry):

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.

8 participants