You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: app/development/DEVELOPMENT.md
+3-17Lines changed: 3 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,17 +5,14 @@
5
5
It is possible to install and run Seedvault in an emulator. This is likely the path of least resistance, since you don't need to build AOSP from source to make and test code changes.
6
6
7
7
It's also helpful for quickly testing Seedvault on newer versions of Android.
8
-
Please note that this process has only been tested on Linux.
8
+
9
+
Please note that this process has only been tested on Linux. If the scripts break with newer versions, try looking at the changes made to the pipeline defined in [.cirrus.yaml](../../.cirrus.yml).
9
10
10
11
### Setup
11
12
12
13
After opening the project in Android Studio, try running the `app:provisionEmulator` Gradle task.
13
14
14
-
This task runs the script in `scripts/provision_emulator.sh`:
Once the emulator is provisioned and running, you should be able to use the `app:installEmulatorRelease`
34
-
Gradle task to install updates.
35
-
36
-
This task depends on `app:assembleRelease` and runs the script in `scripts/install_app.sh`:
37
-
38
-
```bash
39
-
./app/development/scripts/install_app.sh
40
26
```
41
27
42
28
There's also an Android Studio [runtime configuration](https://developer.android.com/studio/run/rundebugconfig)`app-emulator` which will build, install, and automatically launch the `com.stevesoltys.seedvault.settings.SettingsActivity` as if you clicked `Backup` in settings.
0 commit comments