Producing an Android Build
Last updated
Was this helpful?
Last updated
Was this helpful?
Moropo supports running tests on Android using a .apk
build file.
Please note:
Play Store Android App Bundles (.aab
) files are not supported - you must upload a .apk
file
Your .apk
should be compatible with architecture
You can use a Debug or Release build set to use any backend environment.
Many Moropo users configure different test setups for different build types. For example:
a Debug build using your Dev Environment that runs a regression suite on each pull request for a single device
a Release build using your Staging Environment that runs a full test suite before each production release across a wide range of devices
.apk
If you're comfortable with the terminal and have a natively-built Android app, you can use to produce your build file:
To produce a debug build, run ./gradlew assembleDebug
in your terminal.
To produce a release build, run ./gradlew assembleRelease
in your terminal.
The .apk
will be exported to your configured output directory, typically: ~/build/outputs/apk/
.apk
Launch Android Studio
Open your project
Wait for your build to complete.
Press the locate button on the notification (bottom right) to open your file system and access the .apk
.apk
Ensure your eas.config
includes the correct setting:
Run EAS via your terminal to trigger the build:
.apk
If your app is built using Flutter, you can use the flutter
command line inside your terminal.
To produce a Debug build, run flutter build apk --debug
.
To produce a Release build, run flutter build apk
.
Your .apk
will appear in the ./build/app/outputs/
folder.
Click on the Build menu in the top bar, then select Build Bundle(s) / APK(s), then Build APK(s).
If your app is built using React Native, you can use to build your app.
Note: EAS allows a .apk
to be produced using various config options; read the .