Revyl’s cloud emulators are
x86_64 and the APK must be debuggable. See
Artifact Requirements for the full
rules and rationale. Default ./gradlew assembleDebug satisfies both — you
only need to revisit this if you’ve customized abiFilters or are uploading
release builds.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
- Go to Builds page
- Click Upload Build
- Select Android
- Drag and drop your
.apk - Done!
Build via Command Line
Build Variants
Authenticated Test States
Revyl launch variables are available to Android emulator apps as launch intent string extras. Use them to gate a test-onlymyapp://revyl-auth deep link.
See Auth Bypass Deep Links for the Kotlin snippet.
Troubleshooting
APK won't install on the cloud emulator
APK won't install on the cloud emulator
Revyl’s cloud emulators are See Artifact Requirements for details.
x86_64. The APK must include x86_64 in
its ABI set. Default debug builds ship all ABIs in one fat APK — only
an issue if you’ve narrowed abiFilters.If you need an ABI filter, include x86_64:APK not found after build
APK not found after build
Check these locations:Or search for APK files:
Gradle build fails
Gradle build fails
Clean and rebuild:
'gradlew' command not found
'gradlew' command not found
Use the wrapper in your project:If missing, regenerate:
Build succeeds but APK won't install on Revyl
Build succeeds but APK won't install on Revyl
Verify the APK contains an If your APK is
x86_64 slice:arm64-v8a-only, rebuild without abiFilters (or with
x86_64 included). See Artifact Requirements.