osu.Android.props

<Project>
  <PropertyGroup>
    <SupportedOSPlatformVersion>33.0</SupportedOSPlatformVersion>
    <!-- arm64-v8a only.  Modern Android devices are 99%+ arm64; 32-bit arm32 (armeabi-v7a)
         adds ~200 MB of duplicate native libraries for negligible device coverage.
         x86 was already removed — modern x86_64 emulators run arm64 via translation. -->
    <RuntimeIdentifiers>android-arm64</RuntimeIdentifiers>
    <AndroidPackageFormat>apk</AndroidPackageFormat>
    <!-- CJK and Mideast encodings are needed for song metadata display.
         Rare covers supplementary Unicode blocks. West is the default Latin set. -->
    <MandroidI18n>CJK;Mideast;Rare;West;Other;</MandroidI18n>
    <AndroidHttpClientHandlerType>Xamarin.Android.Net.AndroidMessageHandler</AndroidHttpClientHandlerType>
    <!-- NullabilityInfoContextSupport is disabled by default for Android -->
    <NullabilityInfoContextSupport>true</NullabilityInfoContextSupport>
    <EmbedAssembliesIntoApk>true</EmbedAssembliesIntoApk>
    <!-- Do NOT enable AndroidEnableMarshalMethods on .NET 10 with profiled AOT + trimming.
         The build-time P/Invoke stub generator can produce stubs that crash in native code
         when combined with partial AOT and trimmed assemblies — the crash bypasses managed
         exception handling entirely, resulting in silent SIGSEGV/SIGABRT with no crash logs.
         This is especially dangerous for apps with complex interop (UnmanagedCallersOnly,
         unmanaged function pointers, reflection-based handle discovery).
         The default runtime-generated trampolines are slower but proven reliable. -->
    <AndroidEnableMarshalMethods>false</AndroidEnableMarshalMethods>
    <NoWarn>$(NoWarn);NU1608;XA4301</NoWarn>
  </PropertyGroup>

  <!-- Release-only optimisations: AOT for low-latency gameplay, trimming for smaller APK.
       Suppress trim analysis warnings because the project uses reflection extensively
       (Newtonsoft.Json, Realm, AutoMapper, RuntimeBinder). -->
  <PropertyGroup Condition="'$(Configuration)' == 'Release'">
    <RunAOTCompilation>true</RunAOTCompilation>
    <AndroidEnableProfiledAot>true</AndroidEnableProfiledAot>
    <!-- Do NOT use EnableLLVM with profiled AOT on .NET 10.
         The LLVM backend generates internally-inconsistent PLT (Procedure Linkage Table)
         entries when only a subset of methods is AOT-compiled (profiled AOT).  This causes
         'plt_entry not met' assertions in aot-runtime.c at startup (SIGABRT on SDLThread).
         The default Mono AOT compiler handles partial-image PLT generation correctly. -->
    <SuppressTrimAnalysisWarnings>true</SuppressTrimAnalysisWarnings>
    <PublishTrimmed>true</PublishTrimmed>
    <TrimMode>partial</TrimMode>
    <!-- Keep IL bodies as a fallback for methods not covered by profiled AOT.
         AndroidEnableProfiledAot only AOT-compiles methods in the startup profile; the remaining
         methods require IL for JIT/interpretation.  Stripping IL (AndroidStripILAfterAOT=true)
         removes that fallback, causing 'plt_entry not met' assertions in aot-runtime.c when
         the runtime encounters an un-AOT'd method (observed on .NET Timer thread at startup).
         The ~20-30 MB size saving is not worth the crash risk. -->
    <AndroidStripILAfterAOT>false</AndroidStripILAfterAOT>
    <!-- Compress managed assemblies inside the APK (LZ4).  Android extracts them on first run
         but the download/APK size is significantly smaller. -->
    <AndroidEnableAssemblyCompression>true</AndroidEnableAssemblyCompression>
    <!-- Don't ship PDB files in the APK — they add ~15-20 MB.
         Stack traces still work via embedded metadata. -->
    <DebugType>none</DebugType>
    <DebugSymbols>false</DebugSymbols>
  </PropertyGroup>

  <ItemGroup Condition="'$(Configuration)' == 'Release'">
    <!-- Force Microsoft.CSharp into the trimmer input graph (.NET 10+).          -->
    <!-- A bare TrimmerRootAssembly is ignored if the assembly is not in the      -->
    <!-- linker's input set; adding this reference ensures it is included.       -->
    <PackageReference Include="Microsoft.CSharp" Version="4.7.0" NoWarn="NU1510" />
    <TrimmerRootAssembly Include="Microsoft.CSharp" RootMode="all" />
    <!-- Preserve ppy.Veldrid.SPIRV from trimming.  The trimmer does not trace the
         CrossCompileTarget enum usage in osu.Framework's VeldridShader/GLShader correctly
         (the reference crosses assembly boundaries via a ProjectReference chain), causing
         TypeLoadException: 'Could not resolve type Veldrid.SPIRV.CrossCompileTarget' at
         startup when the renderer tries to compile shaders. -->
    <TrimmerRootAssembly Include="ppy.Veldrid.SPIRV" RootMode="all" />
  </ItemGroup>

  <ItemGroup>
    <PackageReference Include="ppy.osu.Framework.Android" Version="2026.421.1" />
  </ItemGroup>

  <PropertyGroup>
    <!-- Fody does not handle Android build well, and warns when unchanged.
         Since Realm objects are not declared directly in Android projects, simply disable Fody. -->
    <DisableFody>true</DisableFody>
  </PropertyGroup>

  <!-- Fix for .NET 10 Android AOT misclassifying native .so assets in runtime pack.
       Only .so files need the AssetType override — the previous broader filter
       (all non-DLL, non-PDB) incorrectly reclassified signing metadata and config
       files, which corrupted the APK signature (INSTALL_PARSE_FAILED_NO_CERTIFICATES).
       Scoped to Release only to avoid interfering with Debug builds. -->
  <Target Name="FixRuntimePackAssetTypes" AfterTargets="ResolveRuntimePackAssets;ComputeFilesToPublish;ComputeResolvedFilesToPublishList"
          Condition="'$(Configuration)' == 'Release'">
    <ItemGroup>
      <RuntimePackAsset Update="@(RuntimePackAsset)" Condition="'%(Extension)' == '.so'">
        <AssetType>native</AssetType>
      </RuntimePackAsset>
      <ResolvedFileToPublish Update="@(ResolvedFileToPublish)" Condition="'%(Extension)' == '.so'">
        <AssetType>native</AssetType>
      </ResolvedFileToPublish>
    </ItemGroup>
  </Target>
</Project>