TITLE: Why My First Android App Crashed 14 Times Before Release
I built NetScan Pro to scan local networks for connected devices, but the first 14 builds crashed on launch. The problem wasn't the code — it was the Android SDK setup. I installed Android Studio via Snap, but the SDK was in ~/Android/Sdk, and Gradle couldn't find the build tools without manual path setup.
Each crash log pointed to a different missing dependency: first the NDK, then the CMake tools, then the platform-34 SDK. I spent 3 days fixing environment variables, and the 15th build finally launched without crashing. The APK is now at /home/allnoworg/Desktop/1/app1-netscan-pro/app/build/outputs/apk/debug/app-debug.apk, and it works on every Android 10+ device I've tested.
The lesson here is that tooling matters more than code. You can write perfect Kotlin, but if your build environment is misconfigured, your app is dead on arrival.
Top comments (0)