Five things that broke my Expo releases on Google Play

# reactnative# expo# android# mobile
Five things that broke my Expo releases on Google PlayYuji Numata

Over the past few months I've put more than twenty small Expo apps on Google Play. None of them have...

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. They didn't help, because CMake runs in a separate process.

One line in android/gradle.properties fixed it:

org.gradle.java.home=C:/Program Files/Java/jdk-17
Enter fullscreen mode Exit fullscreen mode

Use forward slashes. With backslashes the path gets mangled and Gradle says your Java home is invalid.

3. Don't upgrade the Expo SDK in place

I bumped the SDK in an existing project. TypeScript passed, tests passed, the release build signed. The app crashed on launch.

A package from the old SDK had stayed in node_modules, and nothing complained until the native side loaded it. I pin the SDK now. Before each release build, a script checks that every installed Expo package belongs to the same SDK.

4. Blocked permissions you forgot about

Some of my apps started without ads, so app.json blocked the advertising ID permission. Months later I added AdMob and declared ad ID usage in Play Console. The release was rejected before review, because the declaration and the manifest disagreed.

If you add ads to an older app, search app.json for blockedPermissions first.

5. Design the "Remove ads" purchase for the bad cases

Checking the purchase once and saving a flag is easy, but refunds never bring the ads back. So the app asks Google Play again on every launch.

That creates the opposite problem. Phones go offline, and Play Billing sometimes just fails to connect. If you treat "no answer" as "not purchased", a paying user sees ads on the train. I keep the last answer and change it only when the store actually replies.

Also acknowledge every purchase. Google refunds one automatically if the app doesn't acknowledge it within three days.

The kit

I got tired of setting this up again for each app, so I turned it into a starter kit. It's Expo SDK 54, Android-first, with no backend. The fixes above are built in, along with a script that refuses to build when the package name is still com.example, the ad IDs are Google's test ones, or the privacy policy URL is missing.

It's paid. You can find it here: https://ykisoftware.gumroad.com/l/bksfs

If you've run into any of these, or something I missed, I'd like to hear about it in the comments.