4KB Memory Page Warning: Upgraded MAUI project with .Net 10 still shows .SO files

Question

4KB Memory Page Warning: Upgraded MAUI project with .Net 10 still shows .SO files

Sreenivasan, Sreejith 840

I have upgraded my MAUI project's .net version to .net 10 from .net 8 to resolve the 4KB memory warning from play store. After upgrade I have generated a new AAB file and change the extension to .zip from .aab. Then I extracted the .zip file and under the base\lib\arm64-v8a I found 16 .so files.

Name of files adding below:

libarc.bin.so
libassembly-store.so
libdatastore_shared_counter.so
libe_sqlite3.so
libHarfBuzzSharp.so
libimage_processing_util_jni.so
libmono-component-marshal-ilgen.so
libmonodroid.so
libmonosgen-2.0.so
libSkiaSharp.so
libsurface_util_jni.so
libSystem.Globalization.Native.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 memory page issue?

Below are the packages I am using in different projects:

.NET MAUI App:

<ItemGroup>
		<PackageReference Include="Autofac.Extensions.DependencyInjection" Version="11.0.0" />
		<PackageReference Include="Autofac" Version="9.1.0" />
		<PackageReference Include="CommunityToolkit.Maui" Version="14.1.1" />
		<PackageReference Include="FFImageLoading.Maui" Version="1.3.2" />
		<PackageReference Include="Microsoft.Maui.Controls" Version="10.0.60" />
		<PackageReference Include="Microsoft.Maui.Controls.Compatibility" Version="10.0.60" />
		<PackageReference Include="Microsoft.Extensions.Logging.Debug" Version="10.0.8" />
		<PackageReference Include="NLog" Version="6.1.3" />
		<PackageReference Include="NLog.Extensions.Logging" Version="6.1.3" />
		<PackageReference Include="Plugin.Firebase" Version="4.2.1" />
		<PackageReference Include="SkiaSharp" Version="3.119.2" />
		<PackageReference Include="SkiaSharp.Views.Maui.Controls" Version="3.119.2" />
		<PackageReference Include="ZXing.Net.Maui" Version="0.7.4" />
		<PackageReference Include="ZXing.Net.Maui.Controls" Version="0.7.4" />
</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.4" />
	<PackageReference Include="SkiaSharp" Version="3.119.2" />
	<PackageReference Include="SkiaSharp.Views.Maui.Controls" Version="3.119.2" /> 
</ItemGroup>

.NET MAUI Class Library:

<ItemGroup>
		<PackageReference Include="akavache" Version="10.0.28" />
		<PackageReference Include="Autofac" Version="9.1.0" />
		<PackageReference Include="CommunityToolkit.Maui" Version="14.1.1" />
		<PackageReference Include="CommunityToolkit.Mvvm" Version="8.4.2" />
		<PackageReference Include="FFImageLoading.Maui" Version="1.3.2" />
		<PackageReference Include="Humanizer" Version="3.0.10" />
		<PackageReference Include="JsonApiSerializer" Version="2.0.1" />
		<PackageReference Include="Microsoft.Maui.Controls" Version="10.0.60" />
		<PackageReference Include="Microsoft.Maui.Controls.Compatibility" Version="10.0.60" />
		<PackageReference Include="Newtonsoft.Json" Version="13.0.4" />
		<PackageReference Include="NLog" Version="6.1.3" />
		<PackageReference Include="Plugin.Firebase" Version="4.2.1" />
		<PackageReference Include="SkiaSharp" Version="3.119.2" />
		<PackageReference Include="SkiaSharp.Views.Maui.Controls" Version="3.119.2" />
		<PackageReference Include="ZXing.Net.Maui" Version="0.7.4" />
		<PackageReference Include="ZXing.Net.Maui.Controls" Version="0.7.4" />
</ItemGroup>

Also when I rebuild the project in release mode I saw below message in output folder:

Android 16 will require 16 KB page sizes, shared library 'libe_sqlite3.so' does not have a 16 KB page size. Please inform the authors of the NuGet package 'SQLitePCLRaw.lib.e_sqlite3.android' version '2.1.9' which contains 'C:\Users\SreenivasanSr.nuget\packages\sqlitepclraw.lib.e_sqlite3.android\2.1.9\lib\net6.0-android31.0\SQLitePCLRaw.lib.e_sqlite3.android.aar'. See https://developer.android.com/guide/practices/page-sizes for more details. Android 16 will require 16 KB page sizes, shared library 'libe_sqlite3.so' does not have a 16 KB page size. Please inform the authors of the NuGet package 'SQLitePCLRaw.lib.e_sqlite3.android' version '2.1.9' which contains 'C:\Users\SreenivasanSr.nuget\packages\sqlitepclraw.lib.e_sqlite3.android\2.1.9\lib\net6.0-android31.0\SQLitePCLRaw.lib.e_sqlite3.android.aar'. See https://developer.android.com/guide/practices/page-sizes for more details.

I am not using any SQLite package, but I am using akavache package, it has a transitive package named akavache.sqlite3. I am using the 10.1.6 version of it. There is a new version (12.0.12) available for this package. but when I install it I am getting below error: I tried to resolve it, but no luck. All the other packages are latest.

The type or namespace name 'BlobCache' does not exist in the namespace 'Akavache' (are you missing an assembly reference?)

0 comments

Answer accepted by question author

Nancy Vo (WICLOUD CORPORATION) 4,845 Microsoft External Staff Moderator

Hello @Sreenivasan, Sreejith ,

Thanks for your question.

The good news is that 15 out of 16 files are already 16KB compliant. These files (libSkiaSharp.so, libmonodroid.so, libmonosgen-2.0.so, libHarfBuzzSharp.so,...) are shipped by Microsoft and the .NET 10 runtime and are already built with correct alignment.

You are not directly using SQLite, but akavache depends on akavache.sqlite3, which pulls in SQLitePCLRaw.lib.e_sqlite3.android v2.1.9 as a transitive dependency. This package ships an old libe_sqlite3.so compiled with 4KB alignment.

I recommend forcing SQLitePCLRaw.lib.e_sqlite3.android to use a newer compliant version. Add this to your MAUI App project and MAUI Class Library .csproj:

<ItemGroup>
  <PackageReference Include="SQLitePCLRaw.bundle_e_sqlite3" Version="3.0.2" />
  <PackageReference Include="SourceGear.sqlite3" Version="3.50.4.2" />
</ItemGroup>

Then clean and rebuild:

dotnet clean
dotnet build -c Release

Akavache v12 is a major breaking release. The static class BlobCache was removed or restructured. Your existing code that references Akavache.BlobCache breaks because the API changed.

Since v10 already works in your project and your only goal is fixing the 16KB warning (which is caused by SQLitePCLRaw, not Akavache itself), do not upgrade Akavache to v12 yet. Just apply the SQLitePCLRaw fix from problem 1 above.

Please try again and let me know if it works.

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

Sreenivasan, Sreejith 840 Reputation points

2026-05-20T06:48:51+00:00

Hi @Nancy Vo (WICLOUD CORPORATION)

I tried as per your suggestion and there is no 16KB message on output box when rebuilding. So I created a build using the command. But I can still see the libe_sqlite3.so under base\lib\arm64-v8a. I hope it will not affect the 16KB warning.

I am using Akavache package only on .NET MAUI Class Library. So do I need to add the fix on both .NET MAUI Class Library and .NET MAUI App?
Nancy Vo (WICLOUD CORPORATION) 4,845 Reputation points Microsoft External Staff Moderator

2026-05-20T08:04:56.73+00:00

Hi @Sreenivasan, Sreejith ,

Regarding libe_sqlite3.so still appearing, this is completely normal. The fix does not remove libe_sqlite3.so from your build, it replaces it with a correctly aligned version. The file will always be there because akavache needs SQLite to function.

Furthermore, you need to add it to the MAUI App project as well. When you build your final .aab, the MAUI App project is the head project, it is the one that produces the final output and resolves all NuGet dependencies.

I hope this helps. Please try again and let me know the result. Also, check whether the message "App does not support the 16KB memory page sizes" still appears. Thank you.
Sreenivasan, Sreejith 840 Reputation points

2026-05-20T09:27:25.0566667+00:00
Hi @Nancy Vo (WICLOUD CORPORATION) Now the message is not appearing.

2 last questions:

When uploading the builds to play store console I am always receiving a warning related to Native code. The warning is "The app bundle contains native code, and you''ve not uploaded debug symbols. We recommend you upload a symbol file to make your crashes and ANR's easier to analyze and debug. " Is this warning has any connection with the 16KB warning?

For me when upload builds to play store the 16KB error or warning will not showing, but when releasing to play store only warning is showing. After processing the build I go to: Release → App bundle explorer the I Open the uploaded bundle and check for any warnings related to 16 KB memory page support. Is this the right way or am I missing anything?
Nancy Vo (WICLOUD CORPORATION) 4,845 Reputation points Microsoft External Staff Moderator

2026-05-20T09:49:52.72+00:00
Hi @Sreenivasan, Sreejith ,

No, these are two completely separate and unrelated warnings. The debug symbols warning simply means Play Console cannot show you detailed stack traces when your app crashes. It does not affect your 16KB compliance, and it will not block your release. You can safely ignore it for now, but it is good practice to upload symbols to make crash debugging easier.

Yes, you are doing it right and you are not missing anything. The App Bundle Explorer is the official way to verify 16KB compliance. If you do not see this warning anywhere:

This app is not compatible with 16 KB page size devices

Your app is fully 16KB compliant and ready to publish.

In case you see any warnings, just let me know. I’m here to help.
Sreenivasan, Sreejith 840 Reputation points

2026-05-20T12:48:02.26+00:00

@Nancy Vo (WICLOUD CORPORATION) Last time also there is no error or warning, but after release play store shows the warning. That's why I am confirming. I have requested to upload the build to team, I will update you the progress ASAP.
Sreenivasan, Sreejith 840 Reputation points

2026-05-20T17:23:25.7966667+00:00
@Nancy Vo (WICLOUD CORPORATION) Looks like we missed something? Any initialization required for the new changes? App is breaking with below exception after adding this.

An error occurred in the vsdbg debug session of project 'C:\Projects\Inventiva-MAUI\Inventiva\Inventiva.csproj': An unhandled exception of type 'Android.Runtime.JavaProxyThrowable' occurred in Mono.Android.Runtime.dll 05-20 21:22:23.116 D/EGL_emulation(10245): app_time_stats: avg=14.40ms min=3.78ms max=28.68ms count=53 05-20 21:22:23.383 W/monodroid-assembly(10245): Shared library 'liblog' not loaded, p/invoke '__android_log_print' may fail 05-20 21:22:23.386 I/MonoDroid(10245): UNHANDLED EXCEPTION: 05-20 21:22:23.403 I/MonoDroid(10245): Android.Runtime.JavaProxyThrowable: Exception of type 'Android.Runtime.JavaProxyThrowable' was thrown. 05-20 21:22:23.404 I/MonoDroid(10245): 05-20 21:22:23.404 I/MonoDroid(10245): --- End of managed Android.Runtime.JavaProxyThrowable stack trace --- 05-20 21:22:23.404 I/MonoDroid(10245): android.runtime.JavaProxyThrowable 05-20 21:22:23.404 I/MonoDroid(10245): The thread '.NET TP Worker' (4) has exited with code 0 (0x0). The thread '.NET TP Worker' (7) has exited with code 0 (0x0). The thread '.NET TP Worker' (14) has exited with code 0 (0x0). 05-20 21:22:23.491 I/Process (10245): Sending signal. PID: 10245 SIG: 9 The program 'Inventiva.dll' has exited with code 0 (0x0). The vsdbg debug session for project 'C:\Projects\Inventiva-MAUI\Inventiva\Inventiva.csproj' has been stopped

I tried by adding below in MAUIProgram.cs, but no luck.

SQLitePCL.Batteries_V2.Init();

Do we really need both SQLite packages? I saw suggestions to remove SourceGear.sqlite3 package.
Sreenivasan, Sreejith 840 Reputation points

2026-05-20T17:26:35.0566667+00:00

@Nancy Vo (WICLOUD CORPORATION)

Another happy news is Google play confirmed it supports 16 KB, so we are good to go.
Nancy Vo (WICLOUD CORPORATION) 4,845 Reputation points Microsoft External Staff Moderator

2026-05-21T03:15:02.05+00:00
Great @Sreenivasan, Sreejith , original problem has been solved.

Regarding the exception being thrown, The JavaProxyThrowable crash is happening because of having two competing native SQLite providers loaded in the same app. Having multiple native SQLite providers causes a conflict at runtime — the app does not know which one to use and crashes.

Your suggestion is correct. Please remove SourceGear.sqlite3 by updating both your MAUI app and MAUI class library .csprj.

Then remove the SourceGear.sqlite3 package completely.

Additionally, remove the following line:

SQLitePCL.Batteries_V2.Init();

Please try this and let me know the result. Thank you.
Sreenivasan, Sreejith 840 Reputation points

2026-05-21T06:19:24.2266667+00:00
@Nancy Vo (WICLOUD CORPORATION)

I have removed the SourceGear.sqlite3 package and only kept the SQLitePCLRaw.bundle_e_sqlite3 like below and removed the initialization from MAUIProgram.cs. But still same crash.

<ItemGroup> <PackageReference Include="SQLitePCLRaw.bundle_e_sqlite3" Version="3.0.2" /> </ItemGroup>
Nancy Vo (WICLOUD CORPORATION) 4,845 Reputation points Microsoft External Staff Moderator

2026-05-21T08:29:30.4433333+00:00

Hi @Sreenivasan, Sreejith ,

Please try to downgrade to v2.1.11 and then clean and rebuild.
Sreenivasan, Sreejith 840 Reputation points

2026-05-21T09:50:15.05+00:00

@Nancy Vo (WICLOUD CORPORATION)

Yes it worked, hope this changes (removing and downgrading) will not affect the 16 KB memory page size issue.
Nancy Vo (WICLOUD CORPORATION) 4,845 Reputation points Microsoft External Staff Moderator

2026-05-21T09:54:46.04+00:00

Thank you for your feedback. Please feel free to reach out if you encounter any issues.

1 additional answer

Your answer

Sreenivasan, Sreejith 840 Reputation points

2026-05-20T06:48:51+00:00

Hi @Nancy Vo (WICLOUD CORPORATION)

I tried as per your suggestion and there is no 16KB message on output box when rebuilding. So I created a build using the command. But I can still see the libe_sqlite3.so under base\lib\arm64-v8a. I hope it will not affect the 16KB warning.

I am using Akavache package only on .NET MAUI Class Library. So do I need to add the fix on both .NET MAUI Class Library and .NET MAUI App?
Nancy Vo (WICLOUD CORPORATION) 4,845 Reputation points Microsoft External Staff Moderator

2026-05-20T08:04:56.73+00:00

Hi @Sreenivasan, Sreejith ,

Regarding libe_sqlite3.so still appearing, this is completely normal. The fix does not remove libe_sqlite3.so from your build, it replaces it with a correctly aligned version. The file will always be there because akavache needs SQLite to function.

Furthermore, you need to add it to the MAUI App project as well. When you build your final .aab, the MAUI App project is the head project, it is the one that produces the final output and resolves all NuGet dependencies.

I hope this helps. Please try again and let me know the result. Also, check whether the message "App does not support the 16KB memory page sizes" still appears. Thank you.
Sreenivasan, Sreejith 840 Reputation points

2026-05-20T09:27:25.0566667+00:00

Hi @Nancy Vo (WICLOUD CORPORATION) Now the message is not appearing.

2 last questions:

When uploading the builds to play store console I am always receiving a warning related to Native code. The warning is "The app bundle contains native code, and you''ve not uploaded debug symbols. We recommend you upload a symbol file to make your crashes and ANR's easier to analyze and debug. " Is this warning has any connection with the 16KB warning?

For me when upload builds to play store the 16KB error or warning will not showing, but when releasing to play store only warning is showing. After processing the build I go to: Release → App bundle explorer the I Open the uploaded bundle and check for any warnings related to 16 KB memory page support. Is this the right way or am I missing anything?
Nancy Vo (WICLOUD CORPORATION) 4,845 Reputation points Microsoft External Staff Moderator

2026-05-20T09:49:52.72+00:00

Hi @Sreenivasan, Sreejith ,

No, these are two completely separate and unrelated warnings. The debug symbols warning simply means Play Console cannot show you detailed stack traces when your app crashes. It does not affect your 16KB compliance, and it will not block your release. You can safely ignore it for now, but it is good practice to upload symbols to make crash debugging easier.

Yes, you are doing it right and you are not missing anything. The App Bundle Explorer is the official way to verify 16KB compliance. If you do not see this warning anywhere:

This app is not compatible with 16 KB page size devices

Your app is fully 16KB compliant and ready to publish.

In case you see any warnings, just let me know. I’m here to help.
Sreenivasan, Sreejith 840 Reputation points

2026-05-20T12:48:02.26+00:00

@Nancy Vo (WICLOUD CORPORATION) Last time also there is no error or warning, but after release play store shows the warning. That's why I am confirming. I have requested to upload the build to team, I will update you the progress ASAP.
Sreenivasan, Sreejith 840 Reputation points

2026-05-20T17:23:25.7966667+00:00

@Nancy Vo (WICLOUD CORPORATION) Looks like we missed something? Any initialization required for the new changes? App is breaking with below exception after adding this.

An error occurred in the vsdbg debug session of project 'C:\Projects\Inventiva-MAUI\Inventiva\Inventiva.csproj': An unhandled exception of type 'Android.Runtime.JavaProxyThrowable' occurred in Mono.Android.Runtime.dll 05-20 21:22:23.116 D/EGL_emulation(10245): app_time_stats: avg=14.40ms min=3.78ms max=28.68ms count=53 05-20 21:22:23.383 W/monodroid-assembly(10245): Shared library 'liblog' not loaded, p/invoke '__android_log_print' may fail 05-20 21:22:23.386 I/MonoDroid(10245): UNHANDLED EXCEPTION: 05-20 21:22:23.403 I/MonoDroid(10245): Android.Runtime.JavaProxyThrowable: Exception of type 'Android.Runtime.JavaProxyThrowable' was thrown. 05-20 21:22:23.404 I/MonoDroid(10245): 05-20 21:22:23.404 I/MonoDroid(10245): --- End of managed Android.Runtime.JavaProxyThrowable stack trace --- 05-20 21:22:23.404 I/MonoDroid(10245): android.runtime.JavaProxyThrowable 05-20 21:22:23.404 I/MonoDroid(10245): The thread '.NET TP Worker' (4) has exited with code 0 (0x0). The thread '.NET TP Worker' (7) has exited with code 0 (0x0). The thread '.NET TP Worker' (14) has exited with code 0 (0x0). 05-20 21:22:23.491 I/Process (10245): Sending signal. PID: 10245 SIG: 9 The program 'Inventiva.dll' has exited with code 0 (0x0). The vsdbg debug session for project 'C:\Projects\Inventiva-MAUI\Inventiva\Inventiva.csproj' has been stopped

I tried by adding below in MAUIProgram.cs, but no luck.

SQLitePCL.Batteries_V2.Init();

Do we really need both SQLite packages? I saw suggestions to remove SourceGear.sqlite3 package.
Sreenivasan, Sreejith 840 Reputation points

2026-05-20T17:26:35.0566667+00:00

@Nancy Vo (WICLOUD CORPORATION)

Another happy news is Google play confirmed it supports 16 KB, so we are good to go.
Nancy Vo (WICLOUD CORPORATION) 4,845 Reputation points Microsoft External Staff Moderator

2026-05-21T03:15:02.05+00:00

Great @Sreenivasan, Sreejith , original problem has been solved.

Regarding the exception being thrown, The JavaProxyThrowable crash is happening because of having two competing native SQLite providers loaded in the same app. Having multiple native SQLite providers causes a conflict at runtime — the app does not know which one to use and crashes.

Your suggestion is correct. Please remove SourceGear.sqlite3 by updating both your MAUI app and MAUI class library .csprj.

Then remove the SourceGear.sqlite3 package completely.

Additionally, remove the following line:

SQLitePCL.Batteries_V2.Init();

Please try this and let me know the result. Thank you.
Sreenivasan, Sreejith 840 Reputation points

2026-05-21T06:19:24.2266667+00:00

@Nancy Vo (WICLOUD CORPORATION)

I have removed the SourceGear.sqlite3 package and only kept the SQLitePCLRaw.bundle_e_sqlite3 like below and removed the initialization from MAUIProgram.cs. But still same crash.

<ItemGroup> <PackageReference Include="SQLitePCLRaw.bundle_e_sqlite3" Version="3.0.2" /> </ItemGroup>
Nancy Vo (WICLOUD CORPORATION) 4,845 Reputation points Microsoft External Staff Moderator

2026-05-21T08:29:30.4433333+00:00

Hi @Sreenivasan, Sreejith ,

Please try to downgrade to v2.1.11 and then clean and rebuild.
Sreenivasan, Sreejith 840 Reputation points

2026-05-21T09:50:15.05+00:00

@Nancy Vo (WICLOUD CORPORATION)

Yes it worked, hope this changes (removing and downgrading) will not affect the 16 KB memory page size issue.
Nancy Vo (WICLOUD CORPORATION) 4,845 Reputation points Microsoft External Staff Moderator

2026-05-21T09:54:46.04+00:00

Thank you for your feedback. Please feel free to reach out if you encounter any issues.

Answer 1

libe_sqlite3.so is the library that triggers the 16 KB page size warning.

The build output explicitly identifies it:

Android 16 will require 16 KB page sizes, shared library 'libe_sqlite3.so' does not have a 16 KB page size. Please inform the authors of the NuGet package 'SQLitePCLRaw.lib.e_sqlite3.android' version '2.1.9'...

So among the .so files listed, libe_sqlite3.so is the one causing the issue. The others in the list are not mentioned by the tooling as problematic.

libe_sqlite3.so comes from the SQLitePCLRaw.lib.e_sqlite3.android package, which is being pulled in transitively by Akavache (via akavache.sqlite3). Updating Akavache to a version that depends on a newer SQLitePCLRaw.lib.e_sqlite3.android (with 16 KB–compatible binaries) is the correct direction.

The error after updating Akavache:

The type or namespace name 'BlobCache' does not exist in the namespace 'Akavache'

indicates a breaking change in the newer Akavache version (API surface changed, BlobCache removed or moved). Resolving that requires updating the application code to the new Akavache API (for example, replacing Akavache.BlobCache usages with the new recommended cache access pattern for that version) or, if that is not feasible, switching to another caching library that already ships 16 KB–compatible native binaries.

The .NET 10 upgrade and the other .so files listed are not the source of the 16 KB page size warning; the warning is specifically tied to libe_sqlite3.so from SQLitePCLRaw.lib.e_sqlite3.android.

References:

Share via

4KB Memory Page Warning: Upgraded MAUI project with .Net 10 still shows .SO files

1 additional answer

Your answer