Over the past few months I've put more than twenty small Expo apps on Google Play. None of them have a backend. They keep data on the phone and earn from one banner, and some sell a single "Remove ads" purchase.
They're simple apps, but the release side kept tripping me up. These five cost me the most time.
1. The first release build signs with the debug key
expo prebuild generates an Android project whose release build is signed with the debug keystore. Gradle doesn't warn you. The build succeeds, and Play Console rejects the upload because it's debug-signed.
You need your own upload key and a signing config for release. I keep that in a small config plugin, so it survives expo prebuild --clean , which deletes the whole android/ folder.
2. Pin the JDK
My machine's default JDK was 24. With it, the CMake step for some native modules prints a warning about a restricted method, and the Android Gradle Plugin treats that warning as a failure. I tried JVM flags first.…