-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: New mobile Flask Build Type #7837
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #7837 +/- ##
==========================================
+ Coverage 37.44% 37.46% +0.02%
==========================================
Files 1052 1052
Lines 28192 28202 +10
Branches 2517 2517
==========================================
+ Hits 10556 10566 +10
Misses 17037 17037
Partials 599 599 ☔ View full report in Codecov by Sentry. |
0843d01
to
7c87724
Compare
E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/eb8499b8-c6f5-4604-a873-8a273a776b6c |
3e43f3e
to
8f7010c
Compare
From a general point of view, Flask build should point to Dev/Test/Staging or Production services, eg: swaps, ramp? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some minor comments
E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/8384a612-ea83-45a2-8f14-44581c9f85ef |
@wachunei as clarified on slack, we want to have all the ramps environments pointing to the same production end point when flask is released to stores. |
8f7010c
to
0fcadb5
Compare
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
No top level dependency changes detected. Learn more about Socket for GitHub ↗︎ |
7d61ffc
to
bd3687f
Compare
4e46766
to
5689076
Compare
b315904
to
9f8bb52
Compare
Kudos, SonarCloud Quality Gate passed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
This change enables a new build type for MetaMask mobile. This new build is called
flask
and will be used for the canary distribution of features, namely snaps. These builds will be distributed through the google play store as a new app listing on android, and through tetsflight on iOS. These builds already exist through the work of mobile snaps. This PR pulls in thenon snaps
related code for creating these builds. The end result is new "flavour" of metamask, that is identical to the main build. Once we merge code fencing into main, we can then start merging snaps code into then flask build without effecting the main build.Bitrise
deploy android to store
to fail since we need Dan Finlay to help us setup the last part of the pipeline. APKS and IPA are present in the artifacts and iOS has been uploaded to testflight.Testflight
Main build
do not effect production releases
. You can test this out on Testflightv7.12.1 1213
.RPReplay_Final1700791919.MP4
Flask Build
version 0.0.4 1212
RPReplay_Final1700780718.MP4
Related issues
Progresses: https://github.com/MetaMask/accounts-planning/issues/143
Manual testing steps iOS
yarn setup
yarn watch:clean
MetaMask-Flask
as your new variantyarn run start:ios:flask
MetaMask Flask
Manual testing steps Android
yarn setup
yarn watch:clean
View/Tool window/Variants
yarn run start:android:flask
MetaMask Flask
Screenshots/Recordings
Android
iOS
Pre-merge author checklist
Pre-merge reviewer checklist