App does not support the 16KB memory page sizes

Question

App does not support the 16KB memory page sizes

Sreenivasan, Sreejith 740

I got the below error message from the play store for my xamarin forms application:
User's image

I am migrating it to MAUI now. So is the MAUI version fix this issue?

Below are the packages I am using in the MAUI version.

.NET MAUI App:

<ItemGroup>
	<PackageReference Include="Autofac.Extensions.DependencyInjection" Version="8.0.0" />
	<PackageReference Include="Autofac" Version="8.0.0" />
	<PackageReference Include="CommunityToolkit.Maui" Version="8.0.0" />
	<PackageReference Include="FFImageLoading.Maui" Version="1.3.1" />
	<PackageReference Include="Microsoft.Maui.Controls" Version="$(MauiVersion)" />
	<PackageReference Include="Microsoft.Maui.Controls.Compatibility" Version="$(MauiVersion)" />
	<PackageReference Include="Microsoft.Extensions.Logging.Debug" Version="8.0.1" />
	<PackageReference Include="NLog" Version="6.0.2" />
	<PackageReference Include="NLog.Extensions.Logging" Version="5.2.0" />
	<PackageReference Include="Plugin.Firebase" Version="3.1.4" />
	<PackageReference Include="SkiaSharp" Version="3.116.1" />
	<PackageReference Include="SkiaSharp.Views.Maui.Controls" Version="3.116.1" />
	<PackageReference Include="ZXing.Net.Maui" Version="0.4.0" />
	<PackageReference Include="ZXing.Net.Maui.Controls" Version="0.4.0" />
</ItemGroup>

<ItemGroup Condition="'$(TargetFramework)' == 'net8.0-android'">
  <PackageReference Include="Xamarin.AndroidX.Activity.Ktx">
    <Version>1.10.1.2</Version>
  </PackageReference>
  <PackageReference Include="Xamarin.AndroidX.Collection.Ktx">
    <Version>1.5.0.2</Version>
  </PackageReference>
  <PackageReference Include="Xamarin.AndroidX.Lifecycle.LiveData">
    <Version>2.8.7.4</Version>
  </PackageReference>
  <PackageReference Include="Xamarin.AndroidX.Lifecycle.Runtime.Ktx">
    <Version>2.8.7.4</Version>
  </PackageReference>
  <PackageReference Include="Xamarin.AndroidX.Lifecycle.ViewModel.Ktx">
    <Version>2.8.7.4</Version>
  </PackageReference>
</ItemGroup>

.NET Class Library:

  <ItemGroup>
    <PackageReference Include="JsonApiSerializer" Version="2.0.1" />
    <PackageReference Include="Microsoft.CSharp" Version="4.7.0" />
    <PackageReference Include="Newtonsoft.Json" Version="13.0.3" />
	<PackageReference Include="SkiaSharp" Version="3.116.1" />
	<PackageReference Include="SkiaSharp.Views.Maui.Controls" Version="3.116.1" />
  </ItemGroup>

.NET MAUI Class Library:

<ItemGroup>
	<PackageReference Include="akavache" Version="10.0.28" />
	<PackageReference Include="Autofac" Version="8.0.0" />
	<PackageReference Include="CommunityToolkit.Maui" Version="8.0.0" />
	<PackageReference Include="FFImageLoading.Maui" Version="1.3.1" />
	<PackageReference Include="Humanizer" Version="2.14.1" />
	<PackageReference Include="JsonApiSerializer" Version="2.0.1" />
	<PackageReference Include="Microsoft.Maui.Controls" Version="$(MauiVersion)" />
	<PackageReference Include="Microsoft.Maui.Controls.Compatibility" Version="$(MauiVersion)" />
	<PackageReference Include="Newtonsoft.Json" Version="13.0.3" />
	<PackageReference Include="NLog" Version="6.0.2" />
	<PackageReference Include="Plugin.Firebase" Version="3.1.4" />
	<PackageReference Include="SkiaSharp" Version="3.116.1" />
	<PackageReference Include="SkiaSharp.Views.Maui.Controls" Version="3.116.1" />
	<PackageReference Include="ZXing.Net.Maui" Version="0.4.0" />
	<PackageReference Include="ZXing.Net.Maui.Controls" Version="0.4.0" />
</ItemGroup>
<ItemGroup Condition="'$(TargetFramework)' == 'net8.0-android'">
	<PackageReference Include="Xamarin.AndroidX.CardView" Version="1.0.0.21" />
	<PackageReference Include="Xamarin.OpenTok.Android">
	  <Version>2.18.1</Version>
	</PackageReference>
</ItemGroup>

<ItemGroup Condition="'$(TargetFramework)' == 'net8.0-android'">
  <PackageReference Include="Xamarin.AndroidX.Activity.Ktx">
    <Version>1.10.1.2</Version>
  </PackageReference>
  <PackageReference Include="Xamarin.AndroidX.Biometric">
    <Version>1.1.0.29</Version>
  </PackageReference>
  <PackageReference Include="Xamarin.AndroidX.Collection.Ktx">
    <Version>1.5.0.2</Version>
  </PackageReference>
  <PackageReference Include="Xamarin.AndroidX.Lifecycle.LiveData">
    <Version>2.8.7.4</Version>
  </PackageReference>
  <PackageReference Include="Xamarin.AndroidX.Lifecycle.Runtime.Ktx">
    <Version>2.8.7.4</Version>
  </PackageReference>
  <PackageReference Include="Xamarin.AndroidX.Lifecycle.ViewModel.Ktx">
    <Version>2.8.7.4</Version>
  </PackageReference>
</ItemGroup>

Nancy Vo (WICLOUD CORPORATION) 2,305 Reputation points Microsoft External Staff Moderator

2026-04-08T11:02:53.4533333+00:00

Hello @Sreenivasan, Sreejith ,

I will look into this and I will get back to you as soon as possible.
Sreenivasan, Sreejith 740 Reputation points

2026-04-08T12:42:15.6733333+00:00

@Nancy Vo (WICLOUD CORPORATION) Thanks Nancy

I have raised another question now and it is deleted, is there a way to make it undelete?
Nancy Vo (WICLOUD CORPORATION) 2,305 Reputation points Microsoft External Staff Moderator

2026-04-09T06:45:40.2266667+00:00

Hi @Sreenivasan, Sreejith ,

I have checked the thread history, and I cannot see who deleted your thread. I suggest that you avoid providing overly long logs or code snippets. Instead, share only the essential information, and if you need to provide detailed logs or code, please send them via a private message rather than posting them in a comment.

3 answers

Your answer

Nancy Vo (WICLOUD CORPORATION) 2,305 Reputation points Microsoft External Staff Moderator

2026-04-08T11:02:53.4533333+00:00

Hello @Sreenivasan, Sreejith ,

I will look into this and I will get back to you as soon as possible.
Sreenivasan, Sreejith 740 Reputation points

2026-04-08T12:42:15.6733333+00:00

@Nancy Vo (WICLOUD CORPORATION) Thanks Nancy

I have raised another question now and it is deleted, is there a way to make it undelete?
Nancy Vo (WICLOUD CORPORATION) 2,305 Reputation points Microsoft External Staff Moderator

2026-04-09T06:45:40.2266667+00:00

Hi @Sreenivasan, Sreejith ,

I have checked the thread history, and I cannot see who deleted your thread. I suggest that you avoid providing overly long logs or code snippets. Instead, share only the essential information, and if you need to provide detailed logs or code, please send them via a private message rather than posting them in a comment.

Answer 1

Nancy Vo (WICLOUD CORPORATION) 2,305 Microsoft External Staff Moderator

Hi @Sreenivasan, Sreejith ,

Thank you for your inquiry.

The Play Store warning is because some native libraries in your app are still built for the old 4 KB memory pages. Google requires 16 KB support for apps targeting Android 15+. You can refer to this article for more details.

Migrating to MAUI is a great step, but we still need to fix the native parts.

I recommend upgrading the whole project to .NET MAUI 9 or 10. Because these versions support 16KB automatically. .NET MAUI 8 is already out of support, so you are likely to face multiple issues when using an outdated version.

Furthermore, update these packages to their latest versions:

SkiaSharp and SkiaSharp.Views.Maui.Controls
ZXing.Net.Maui
FFImageLoading.Maui
Plugin.Firebase
Xamarin.OpenTok.Android

After updating, clean the project, build a new AAB, and upload to Internal Testing in Play Console. The warning should disappear.

I hope this addresses your question. If this response was helpful, please consider following the guidance to provide feedback.

Sreenivasan, Sreejith 740 Reputation points

2026-04-09T06:59:25.46+00:00

@Nancy Vo (WICLOUD CORPORATION) Thank you very much for your support.

One last query, Is there a way to check this issue will occur or not using the AAB file?
Nancy Vo (WICLOUD CORPORATION) 2,305 Reputation points Microsoft External Staff Moderator

2026-04-09T07:25:13.8866667+00:00
Hello @Sreenivasan, Sreejith ,

I suggest using Google’s bundletool (a free command-line tool). After building your AAB in Visual Studio, run this command in the terminal:

java -jar bundletool.jar dump config --bundle=your-app.aab | grep alignment

If the output shows PAGE_ALIGNMENT_16K, your AAB is properly requesting 16 KB alignment and should be compliant.

If it shows PAGE_ALIGNMENT_4K, some native libraries are still using the old 4 KB alignment, and the issue will likely appear on 16 KB devices or trigger the warning in Google Play.

Always do a full clean (delete bin and obj folders) + fresh dotnet publish before checking the AAB, so you are testing the latest built files.

I hope this information is helpful to you, and thank you for your time.
Sreenivasan, Sreejith 740 Reputation points

2026-04-09T10:42:50.29+00:00
@Nancy Vo (WICLOUD CORPORATION) I have generated a new AAB file from MAUI project and change the extension to .zip from .aab. Then I extracted the .zip file and under the base\lib\arm64-v8a I found 12 .so files.

Name of files adding below:

libe_sqlite3.so

libHarfBuzzSharp.so

libimage_processing_util_jni.so

libmono-component-marshal-ilgen.so

libmonodroid.so

libmonosgen-2.0.so

libopentok.so

libSkiaSharp.so

libSystem.IO.Compression.Native.so

libSystem.Native.so

libSystem.Security.Cryptography.Native.Android.so

libxamarin-app.so

Is any of these cause the 16 KB issue from MAUI build?

Answer 2

Omkar Pawar 260

Check this link, I think it’s the same and might help you understand it: https://dori-uw-1.kuma-moon.com/en-us/answers/questions/5550569/what-changes-i-would-need-to-release-application-f

0 comments

Answer 3

Migrating to .NET MAUI by itself does not guarantee that the 16 KB page-size issue is fixed. The problem is in one or more native .so libraries inside the NuGet packages used by the app, not in whether the app is Xamarin.Forms or MAUI.

Android 16 on arm64 will require native libraries to use 16 KB page sizes. Any native shared library that is not built with 16 KB alignment must be recompiled and relinked accordingly. Apps that include such libraries (directly or via NuGet packages/AARs) must then be rebuilt to include the fixed binaries.

Key points for the MAUI version:

The .NET MAUI / .NET for Android toolchain supports Android 34+ and is being updated for newer Android versions, but it does not automatically “fix” third‑party native libraries.
Each package that contains native Android libraries (.so files) must provide binaries that comply with the 16 KB page-size requirement. If a package ships non‑compliant native code, the MAUI app will still be non‑compliant.
The official guidance is:
- Identify the offending native shared library reported in the XA0141 warning or Play Console message.
- Contact the author of the NuGet package that contains that library and request a version rebuilt with 16 KB page-size support.
- Update the app to reference the fixed package version and rebuild.

Therefore:

Simply moving from Xamarin.Forms to MAUI does not resolve the policy violation.
The issue is resolved only when all native libraries included in the MAUI app (including those from packages like Xamarin.OpenTok.Android or any other binding/AAR) have been rebuilt for 16 KB page sizes and the app is rebuilt with those versions.

Follow the Android SDK guidance in “Support 16 KB page sizes” and ensure that any package authors whose libraries include native code do the same.

References:

Share via

App does not support the 16KB memory page sizes

3 answers

Your answer