MetaMask / MetaMask/metamask-mobile
Size of Release Build for metamask-mobile Exceeds 500 MB
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
### What is this about?
Certainly! Here's an enhanced version of your message:
Greetings!
I've successfully forked the MetaMask Mobile repository at https://github.com/MetaMask/metamask-mobile and completed all the necessary setup as outlined in the documentation at https://github.com/MetaMask/metamask-mobile#readme.
To customize my build, I've configured my own Sentry credentials in the sentry.properties file and placed a release.keystore file in the android/keystores directory. Following these steps, I executed the commands
yarn setup
yarn build:android:release
Despite trying various commands and even setting **enableSeparateBuildPerCPUArchitecture** to true, I consistently encounter a build size exceeding 500MB.
I would greatly appreciate any insights or suggestions you might have to help optimize the build size. Thank you for your assistance!
### Scenario
_No response_
### Design
_No response_
### Technical Details
_No response_
### Threat Modeling Framework
_No response_
### Acceptance Criteria
_No response_
### References
_No response_
Contributor guide
Research direction
Start by reproducing the issue with `yarn setup` and `yarn build:android:release`, then inspect the Android release configuration around `enableSeparateBuildPerCPUArchitecture` and the produced artifact size. Done means identifying a supported change that brings the release build below 500 MB and verifying the resulting size.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native, typescript
- Domain
- build-system, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100