Branded Android app update no longer supports existing Android 9 users

AppSheet AppSheet Q&A
,
1

I generated a new Android App Bundle for my AppSheet branded app and tried to upload it as an update in Google Play Console.

The current published version supports a minimum SDK of API 28 (Android 9). The newly generated AppSheet bundle has a minimum SDK of API 29 (Android 10) and a target API 35. Google Play Console therefore blocks the rollout with this message:

“You can’t roll out this release because it doesn’t allow any existing users to upgrade to the newly added app bundles.”

I understand that AppSheet generates the Android bundle and that I cannot change the minimum SDK myself.

Could AppSheet provide a branded Android bundle that meets the current Google Play target-API 36 / Android 16 requirement while retaining minimum SDK 28 / Android 9 compatibility? If Android 10 is now the permanent minimum, is there an AppSheet-recommended migration path that preserves the Play Store update path for existing Android 9 users?

The generated bundle also shows Android 15 technical-quality notices related to SafetyNet and edge-to-edge APIs. Are those expected to be addressed in a future AppSheet branded-app build?

2

You may want to take a look at the following article that states that an Android or iOS version will be supported for maximum 7 years by AppSheet.

Android 9 was released in 2018. So it seems to have exceeded the committed support time period.

3

Thanks, I saw that post as well. The play store doesn’t allow for upgrade paths when the target device list changes. I am hoping for a solution that doesn’t require me to create another App in google play store and force all my users to migrate to the new app.

4

I’ll leave my original post on here because we need API 36 (android 16) support but I found the option to include old versions of the app in the release which solves the min sdk issues. :person_facepalming:

Screenshot 2026-08-07 190951
Screenshot 2026-08-07 1909511507×846 41.7 KB

5

Thank you @timAtRidge,

I strongly suggest marking the post as a solution so that we make it easier for others to find this fix if they face a similar issue.