Failure [INSTALL_FAILED_DEPRECATED_SDK_VERSION: App package must target at least SDK version 23, but found 21

[Haider]

 

[jasonbayton]

Context for you - https://bayton.org/android/android-14-minimum-sdk/

🙂

[mattdermody]

I have a feeling this is one of the first of many of these type of posts we're going to see. 

Android 14 is now explicitly blocking lower target build APKs from being installed on devices. The only "workaround" to this is a forced install through ADB. It can't be forced any other way. You will have to work with the app developer to have it updated to be compliant in order for it to be installed.

This will likely be a big problem for some enterprises that have a legacy enterprise application that was developed internally but no longer maintained that are forced into a device refresh to devices running A14+.

[jasonbayton]

And Android 15 bumps it up to min version of 24, so this'll be a moving target forevermore. 

I assume it's going to be one of those things that'll force orgs to either figure out how to get it updated, or abandon the legacy app and redevelop it. Neither being a fun activity, nor cheap I'd imagine, but little choice now save for remaining on old, outdated hardware.

[mattdermody]

It’s going to be a mixed bag but I know a number of end customers that consider their business app more important than what version of Android they’re running and will therefore either keep old devices around or downgrade the ones they can.  It’s easier to downgrade a device to an older Android OS than refactoring a mobile app where the original developer has left the company. Definitely a risky way to run a business but I tend to side with these orgs that Google shouldn’t be the one to decide which apps they’re allowed to install on devices that they own.