When Jetwave was preparing to roll out the Rider by Jetwave app, everything looked perfect on newer Android phones. But then, one of our drivers using an Itel A50 reported that the app crashed immediately after opening.
Instead of delaying the full rollout, we built a quick release APK, sent it directly to the driver, and captured the logs.
In minutes, the issue was traced to a missing 32-bit architecture support.
A single line added to our build file — and the problem disappeared.
That simple local test saved us days of back-and-forth debugging and prevented the same issue from reaching production users.
⚙️ Ease of Deployment: Simple and Direct
Local deployment lets developers and admins share test builds quickly.
Here’s a standard example of how to build and locate your APK for local testing:
# Navigate to your project
cd ~/Desktop/JetRiders
# Build your release APK
cd android
./gradlew assembleRelease
# Open the folder containing your app-release.apk
open app/build/outputs/apk/release/
💡 Tip:
You can confirm your APK is ready with:
ls app/build/outputs/apk/release/
If you see app-release.apk, it’s ready to send to testers.
🧭 The Bigger Picture
When developers test locally, admins gain speed, drivers enjoy a smoother experience, and users get a more reliable app.
It’s a lean, practical system that reduces guesswork and increases confidence before your app hits the world.
At Jetwave, we believe the future of testing isn’t about waiting for approval — it’s about empowering teams to test, fix, and ship smarter.