A Bug or I'm dumb?

[marcussacana]

I'm trying build my Avalonia .NET 6 app for Android, the debug builds works fine,
But release builds, with AOT enabled, throws this exception and my app freeze in the splash screen.

2022-06-11 08:50:50.232 12036-12036/? A/mono-rt: [ERROR] FATAL UNHANDLED EXCEPTION: System.PlatformNotSupportedException: Arg_PlatformNotSupported
        at System.Text.ASCIIUtility.GetIndexOfFirstNonAsciiByte_Intrinsified(Byte* , UIntPtr )
        at System.Text.Unicode.Utf8Utility.GetPointerToFirstInvalidByte(Byte* , Int32 , Int32& , Int32& )
        at System.Text.UTF8Encoding.GetCharCount(Byte* , Int32 )
        at System.String.CreateStringFromEncoding(Byte* bytes, Int32 byteLength, Encoding encoding)
        at System.Text.Encoding.GetString(Byte* , Int32 )
        at System.String.CreateStringForSByteConstructor(Byte* pb, Int32 numBytes)
        at System.String.Ctor(SByte* value)
        at System.Runtime.InteropServices.Marshal.PtrToStringAnsi(IntPtr )
        at Java.Interop.TypeManager.GetClassName(IntPtr )
        at Android.Runtime.JNIEnv.RegisterJniNatives(IntPtr , Int32 , IntPtr , IntPtr , Int32 )

My phone is a ARM64v8 device.

I wanted give a try by excluding the AOT in the System.Private.CoreLib.dll assembly, but I didn't found details about how I can exclude assemblies from AOT, for now, I tried <PublishReadyToRunExclude Include="System.Private.CoreLib.dll" /> but no lucky.

[huoyaoyuan]

This should be a bug, in trimmer or AOT. You shouldn't get into the Intrinsified path when corresponding instruction sets are not enabled.

I wanted give a try by excluding the AOT in the System.Private.CoreLib.dll assembly, but I didn't found details about how I can exclude assemblies from AOT, for now, I tried <PublishReadyToRunExclude Include="System.Private.CoreLib.dll" /> but no lucky.

CoreLib is R2R compiled before shipping into the SDK, but it should still contain the fallback path.

[marcussacana]

I see, In that case Is better wait #41292 be finished before fire a issue?
Since it will change the code around where I got the problem, maybe it will solve the problem, I suppose.

[huoyaoyuan]

The problem would be hidden rather than fixed. I'd suggest you to open an issue to find the root cause.
Remember to try latest .NET 7 preview before opening new one.