[Android] 16KB page-size compatibility for Uno.UI packages?

[nvenluke]

Hello UNO,

I've read your blog post regarding the upcoming Google Play Store requirement:
https://platform.uno/blog/what-android-16-kb-page-size-requirement-means-for-net-developers/

However, we have some apps that are not using the Uno.Sdk; just assortments of Uno nuget packages including Uno.WinUI components. Would you be able to give guidance on which versions of Uno.WinUI are compatible with the 16KB page size?

Concern 📚

Clarification of capabilities 💡

Renderer 🎨

• Skia
• Native

Affected platforms 📱💻🖥️

Android

[jeromelaban]

Thanks for the question. You only need to make sure you run with .NET 9, the uno.sdk is not a requirement for this.

[nvenluke]

Thanks, Jerome.

We're currently targeting net9.0-android35.0
( <TargetFrameworks>net9.0-android35.0;net9.0-ios</TargetFrameworks> in the mobile head .csproj)

...but we're still seeing a large set of native code libraries appearing in the .apk, all of which are showing as incompatible with 16kb-page-size (ie. inspecting them in a viewer shows that each "LOAD" segment has a p_align value of 0x1000).

Github Copilot's assessment of the source packages for each of these:

Native Library	Top-Level Dependency Causing Inclusion	Reasoning
libarc.bin.so	Xamarin.Android runtime	Part of Android runtime, included by default in Xamarin/MAUI Android projects.
libbugsee-native.so	Bugsee	Directly from Bugsee NuGet package (conditional on non-production).
libmono-component-debugger.so	Xamarin.Android runtime	Included by Xamarin.Android for debugging support.
libmono-component-hot_reload.so	Uno.WinUI / Microsoft.Maui.Essentials	Hot reload support, included by Uno/MAUI and Xamarin.Android tooling.
libmono-component-marshal-ilgen.so	Xamarin.Android runtime	Part of Mono runtime for marshaling, included by Xamarin.Android.
libmono-profiler-aot.so	Mono.AotProfiler.Android	Directly from Mono.AotProfiler.Android NuGet package.
libmonodroid.so	Xamarin.Android runtime	Core Mono runtime for Android, always included.
libmonosgen-2.0.so	Xamarin.Android runtime	Core Mono runtime for Android, always included.
libSkiaSharp.so	SkiaSharp	Directly from SkiaSharp NuGet package (iOS only, but may be present in Android as well).
libSystem.Globalization.Native.so	.NET runtime / BCL	Part of .NET base class libraries, always included.
libSystem.IO.Compression.Native.so	.NET runtime / BCL	Part of .NET base class libraries, always included.
libSystem.Native.so	.NET runtime / BCL	Part of .NET base class libraries, always included.
libSystem.Security.Cryptography.Native.Android.so	.NET runtime / BCL	Part of .NET base class libraries, always included.
libxamarin-app.so	Xamarin.Android runtime	App entry point, always included in Xamarin.Android apps.
libxamarin-debug-app-helper.so	Xamarin.Android runtime (Debug builds)	Debug helper, included in debug builds by Xamarin.Android.

I know that for the Skia one in particular, it looks like we can resolve it by updating a top-level Skia package.

For the others - is it your understanding that none of these would be coming in as dependencies of Uno packages? (in particular, there's the libmono-component-hot_reload.so which Copilot thinks could be coming in through Uno.WinUI?)

[jeromelaban]

Thanks for the additional information. It looks like you're analyzing a debug version of a package, do you get the same results with a release build?

[nvenluke]

Yes, I realized that mistake - sorry!

I'm currently trying to do the same analysis on a release/prod version. For some reason (no idea if it's normal) there's a much larger list of .so files in this one - 332 altogether. I'm trying to put together a script because dropping each file into the viewer would take forever.

Sampling of the list has shown many to be already 16KB-page-compatible, including several of those which were present (in non-compatible version) in the debug list. Unsurprisingly, libmono-component-hot_reload.so is not present.

I'll update here when I have the results.