Skip to main content
Revyl accepts x86_64 and arm64-v8a native libraries, and the APK must be debuggable. See Artifact Requirements for the full rules and rationale. Default ./gradlew assembleDebug satisfies these requirements — you only need to revisit this if you’ve customized abiFilters or are uploading release builds.

​
Build Guidance

To use the Dev Loop, a build is required on every code change. The APK is the app — see Dev Loop: Hot reload and rebuild configuration for the full breakdown. Android reinstalls preserve app data (the -r flag is used).

​
Build via the Revyl CLI

​
Prerequisites

  • Revyl CLI installed and authenticated (revyl auth login)

​
Setup

Initialize the project using the Revyl CLI:
This detects the Android build and writes a named profile with its Android recipe. Review or fill in the app ID, commands, and output path before the first build.

​
Run Build

Run a build using: revyl build --profile development --platform android This runs the selected recipe in the cloud. If your profile has a different name, pass it explicitly; no profile is active/default. See Configuration.

​
Advanced Configuration

Revyl makes a best effort to determine the build commands to be used. If the build does not complete successfully modify the build commands manually in the config.yaml file.

​
Build via Android Studio

​
1. Open Project

Launch Android Studio and open your app.

​
2. Build APK

Choose Build → Build Bundle(s) / APK(s) → Build APK(s)
Use debug builds for Revyl. Release/non-debuggable APKs install but disable the State tab and other debug-only inspection paths.

​
3. Locate Build

Click Locate in the bottom-right notification. APK location:

​
4. Upload to Revyl

See Ways to Add Builds to upload the build to Revyl.

​
Troubleshooting

APKs with native libraries must include x86_64 or arm64-v8a. Default debug builds ship compatible ABIs in one fat APK — this is usually only an issue if you’ve narrowed abiFilters.If you need ABI filters, include one or both supported 64-bit ABIs:
See Artifact Requirements for details.
Check these locations:
Or search for APK files:
Clean and rebuild:
Use the wrapper in your project:
If missing, regenerate:
Verify the APK contains an x86_64 or arm64-v8a slice:
If it contains only x86 or armeabi-v7a, rebuild without abiFilters or include a supported 64-bit ABI. See Artifact Requirements.

​
Resources

​
Dev loop

Native Android uses a rebuild-based dev loop. The CLI detects build.gradle / build.gradle.kts and configures ./gradlew assembleDebug. During revyl dev, press [r] to rebuild and reinstall. Typical rebuild cycle: ~30-90s. Reinstalls preserve app data. If an Expo or React Native project is detected as Android Native, run revyl init --detect from the app directory. If detection still cannot resolve the monorepo layout, edit build.framework and the generated profile recipes in .revyl/config.yaml, then run revyl config validate.