Play Store Warning: This release no longer support xxxx devices that were supported in your previous release.

Question

Play Store Warning: This release no longer support xxxx devices that were supported in your previous release.

Sreenivasan, Sreejith 1,025

I am getting the below warning for my MAUI app from play store:
User's image

My Previous version was .net 8 with minSdkVersion 21 and targetSdkVersion 35. My current version is .net 10 with minSdkVersion 23 and targetSdkVersion 36.

I am getting below error when I tried to took the build with minSdkVersion as 21 on .net 10 project.

uses-sdk:minSdkVersion 21 cannot be smaller than version 23 declared in library androidx.lifecycle.runtime Suggestion: increase this project's minSdk version to at least 23

Problem is one of my Android dependencies requires minSdkVersion = 23. But my MAUI project is still building with minSdkVersion = 21.

I even tried below settings on manifest, but this also end with errors.

<manifest xmlns:tools="http://schemas.android.com/tools">

    <uses-sdk
        android:minSdkVersion="21"
        tools:overrideLibrary="androidx.lifecycle.runtime" />

</manifest>

So is increasing Minimum Android Version only fix? In that case how we can manage the xxxx users?

0 comments

2 answers

Your answer

Answer 1

Thank you @Sreenivasan, Sreejith for your question.

Based on the error message, the dependency's minimum SDK requirement appears to be the blocking factor here. If a dependency declares a minimum SDK version of 23, the application cannot be built with a lower minimum SDK version, such as 21, unless that dependency requirement is addressed.

With that in mind, I suggest the following options:

Check whether an earlier version of the dependency or package is available that supports a lower minimum SDK version.
Another approach, although advanced and generally not recommended, would be to inspect the dependency itself and determine whether its minimum SDK requirement can be reduced. Depending on the package, it may be possible to modify or remove functionality that depends on API level 23 so that it can be used with a lower minimum SDK version.
Alternatively, you could look for alternative packages that provide similar functionality while still supporting API level 21.

As a side note on the manifest configuration you tried, tools:overrideLibrary only suppresses the check performed during manifest merging. It does not make the library itself compatible with API levels 21 and 22, and the tooling notes that forcing usage in this way may lead to runtime failures on those devices. For this reason, I would recommend setting it aside and focusing on the options below instead, as they address the dependency requirement itself rather than bypassing the check.

Regarding your second question, the range of devices that can install the application is determined by the effective minimum SDK version, so if the dependency requirement cannot be lowered through one of the options above, those devices would fall outside the supported range, and there is unfortunately no configuration on the .NET MAUI side that would keep them supported.

One point that may be worth evaluating is whether the dependency is used only for a specific feature, as it may be possible to isolate that functionality so that the rest of the application is not affected by its minimum SDK requirement.

In case you are also interested in how previous releases remain available to users on older devices, you may want to check the documentation on the Google Play side.

I hope this helps point you in the right direction. If you found my response helpful or informative, I would greatly appreciate it if you could follow this guide for your confirmation.

Thank you.

Sreenivasan, Sreejith 1,025 Reputation points

2026-09-11T09:12:48.86+00:00

@Nguyen Dam (WICLOUD CORPORATION) Let me check and get back to you.

Answer 2

Yes. In this scenario, increasing the minimum Android version is the required fix.

The build error is expected because a referenced Android library declares minSdkVersion 23, so the app cannot ship with minSdkVersion 21. The warning from Google Play is therefore a consequence of raising the app’s minimum supported Android version.

For modern .NET Android and .NET MAUI projects, the minimum Android version should be set in the project file with SupportedOSPlatformVersion, rather than relying on <uses-sdk/> in AndroidManifest.xml. That value maps to android:minSdkVersion at build time.

Use a project setting like this in the Android target:

<PropertyGroup>
  <TargetFramework>net10.0-android</TargetFramework>
  <SupportedOSPlatformVersion>23</SupportedOSPlatformVersion>
</PropertyGroup>

If android:minSdkVersion is also set manually in AndroidManifest.xml, it must match the project setting. Keeping conflicting values in the manifest can cause build or packaging problems.

About the affected users:

Users on devices below the new minimum version will not be able to install new updates.
Existing users on those unsupported devices can continue using the version already installed, but they will not receive future app updates.
The recommended action is to notify those users that newer app versions require a newer Android OS.

This is consistent with platform guidance that when the minimum supported Android API level is raised, apps can no longer be installed or run on devices below that level, and users should be informed when updates are no longer available for older Android versions.

So the practical path is:

Set the MAUI project minimum Android version to 23 in the .csproj.
Remove or align any <uses-sdk/> entry in AndroidManifest.xml.
Rebuild and upload the new AAB.
Inform users on Android versions below API 23 that they must upgrade the device OS to receive future app updates.

Using tools:overrideLibrary does not change the fact that the dependency itself requires a higher minimum SDK. The supported app minimum must still be compatible with the libraries included in the app.