Today, Gecko developers need to go through quite a few steps still to build Fenix locally if they make platform changes and want to test them out on mobile apps. ### Steps to reproduce 1. `mach build` 2. Setup `JAVA_HOME` and `ANDROID_HOME` environment variables (because these cannot be found unless you use `mach gradle`). 3. [Generate a signing key](https://developer.android.com/studio/publish/app-signing#generate-key) (with CLI instructions are probably somewhere close to that link). 4. Add `autosignReleaseWithDebugKey` to `mobile/android/{android_app}/local.properties`. 5. `cd mobile/android/fenix` 6. `./gradlew installFenixRelease` ### Expected behaviour * After `mach build`, you should be able to build (from the root or project directory) any of the mobile projects without needing more environment configurations outside of `mach bootstrap`. ### Actual behaviour * You should not need to do step 2, 3, or 5. * At step 6, you should be able to use `mach gradle installFenixRelease` instead. ### Device information * Firefox version: n/a * Android device model: n/a * Android OS version: n/a ### Any additional information? * `ANDROID_HOME` is needed because the `sdk.dir` property in `local.properties` is created by Android Studio. * `JAVA_HOME` is needed if you are going to execute `gradlew` in one of the app projects. * Both of the above would not need to be set if we can get `mach gradle` to recognize these projects from the root gradle.
Bug 1891159 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Today, Gecko developers need to go through quite a few steps still to build Fenix locally if they make platform changes and want to test them out on mobile apps. ### Steps to reproduce 1. `mach build` 2. Setup `JAVA_HOME` and `ANDROID_HOME` environment variables (because these cannot be found unless you use `mach gradle`). 3. [Generate a signing key](https://developer.android.com/studio/publish/app-signing#generate-key) (with CLI instructions are probably somewhere close to that link). 4. Add `autosignReleaseWithDebugKey` to `mobile/android/{android_app}/local.properties`. 5. `cd mobile/android/fenix` 6. `./gradlew installFenixRelease` ### Expected behaviour * After `mach build`, you should be able to build (from the root or project directory) any of the mobile projects without needing more environment configurations outside of `mach bootstrap`. * You should not need to do step 2, 3, or 5. * At step 6, you should be able to use `mach gradle installFenixRelease` instead. ### Device information * Firefox version: n/a * Android device model: n/a * Android OS version: n/a ### Any additional information? * `ANDROID_HOME` is needed because the `sdk.dir` property in `local.properties` is created by Android Studio. * `JAVA_HOME` is needed if you are going to execute `gradlew` in one of the app projects. * Both of the above would not need to be set if we can get `mach gradle` to recognize these projects from the root gradle.