Android Specific Workflow Steps
The steps listed below are specific to the Android build profiles.
You can find the full list of available workflow steps in our workflow marketplace and under each workflow step in this document, you can find the related repository URL, which also includes the documentation for the related step.
Android Build
This step builds your Android application for the architectures specified in your project.
Tip: If you are using Gradle 4.3 and above in your project, you can just use the --scan flag in the build step to enable build scans. For existing projects, you may need to add the Gradle Scan (Gradle Enterprise) plugin. For more information, please refer to https://scans.gradle.com/
Gradle Runner
This step runs given Gradle task.
Android Sign
This step signs your APK or App Bundle with the given Android keystore and exports a binary file compatible with Android devices.
Android App Post-Processor
This step performs necessary system operations to identify and process the Android output binary files.
Android Lint
This step runs lint Gradle tasks on the source files of the project.
Android Build for UI Testing
Builds your test applications with gradlew. Runs ./gradlew clean ${module}:assembleAndroidTest.
Android Unit Tests
This step runs the unit tests of the project.;
Android Dependency Report
This step visualizes the whole dependency tree for every configuration available in the project.
Wait for Android Emulator
This step waits for Android Emulator to boot. You must use this step before running any UI tests.
Bundle Universal Apk
This step generates an universal APK from an AAB.
Detekt
This step runs detekt gradle task.
BrowserStack App Automate - Espresso
Run your Espresso tests on BrowserStack App Automate. You need to add Android Build for UI Testing before this step to create the required $AC_APK_PATH and $AC_TEST_APK_PATH files.
AppSweep Mobile Security Testing
Scan your Android app using AppSweep
App Center Android Distribution
Distribute APK,AAB and mapping files to App Center. You need enter your token, owner, app and group names to distribute your binaries.