Follow-up to #10792 / PR #12127.
Pre-generated framework typemaps (Mono.Android + Java.Interop, anchored on the Java.Lang.Object universe) are consumed correctly in:
- the single/shared universe (Release NativeAOT), and
- the aggregate/per-assembly universe without array maps (
maxArrayRank == 0, e.g. CoreCLR Debug).
The remaining combination — aggregate universe + array maps (maxArrayRank > 0, i.e. Debug NativeAOT) — is not yet wired: RootTypeMapAssemblyGenerator.EmitInitializeWithAggregateTypeMap would need to add the Java.Lang.Object framework universe (and its per-rank __ArrayMapRank{N} array maps) as an extra element alongside the app's per-assembly universes.
Until then, the app build gracefully falls back to scanning Mono.Android/Java.Interop normally for that combination (no speedup, but correct).
Follow-up to #10792 / PR #12127.
Pre-generated framework typemaps (Mono.Android + Java.Interop, anchored on the
Java.Lang.Objectuniverse) are consumed correctly in:maxArrayRank == 0, e.g. CoreCLR Debug).The remaining combination — aggregate universe + array maps (
maxArrayRank > 0, i.e. Debug NativeAOT) — is not yet wired:RootTypeMapAssemblyGenerator.EmitInitializeWithAggregateTypeMapwould need to add theJava.Lang.Objectframework universe (and its per-rank__ArrayMapRank{N}array maps) as an extra element alongside the app's per-assembly universes.Until then, the app build gracefully falls back to scanning Mono.Android/Java.Interop normally for that combination (no speedup, but correct).