MetaMask / MetaMask/metamask-mobile
OTA updates production: use deeplinking to apply OTA updates
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
### What is this about?
If we can upgrade Expo SDK to 54, we can enable EAS updates in runtime. We can use deeplinking for QA to test production EAS updates.
More details in this Expo [thread](https://consensys.slack.com/archives/C07DH19MY0P/p1761762323092839)
### Scenario
_No response_
### Design
_No response_
### Technical Details
_No response_
### Threat Modeling Framework
_No response_
### Acceptance Criteria
_No response_
### Stakeholder review needed before the work gets merged
- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)
### References
_No response_
Contributor guide
Research direction
No repository files, tests, or entry points are identified; start with the linked Expo thread and review the proposed Expo SDK 54, EAS Updates, and deep-linking work. Done should mean QA can use deep linking to test production EAS updates, but acceptance details are not provided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100