As far as I understand, converting IL code to native CPP code does not affect absolutely all classes (judging by the libraries obtained from CPP2IL). For example, AssetBundle in UnityEngine.AssetBundleModule.

Can you elaborate on this?

As far as I understand, converting IL code to native CPP code does not affect absolutely all classes (judging by the libraries obtained from CPP2IL). For example, AssetBundle in UnityEngine.AssetBundleModule.

Can you elaborate on this?

I will try.

I started my research with the reason why the else if-statement branch is used. After fixing the IL code and method references I still got NullPointerException. I assumed that the problem is in the AssetBundle class itself.

Next, in dotPeek I opened UnityEngine.AssetBundleModule from the interop folder, which I got from BepInEx. I checked the differences between UnityEngine.AssetBundleModule.AssetBundle and UnityEngine.GameObject. AssetBundle has no constructor, only a static one.

I thought this was incorrect and checked the library from Unity itself. In it, AssetBundle has a private constructor that is sent to the constructor of the parent UnityEngine.Object.

Assuming that the problem was in the generation, I started checking Il2CPPInterop.Generator. The search led me to the class Passes.Pass10CreateTypedefs. After checking what classes were present during generation, I found out that from the UnityEngine.AssetBundleModule module, only AssetBundleCreateRequest, AssetBundleRecompressOperation and AssetBundleRequest exist.

After tracking where gameAssembly comes from, I moved on to the CPP2IL files. In the generated files from GameAssembly.dll and metadata.dat, I checked UnityEngine.AssetBundleModule.

So, I assumed that Unity wasn't translating all of its classes into CPP code during compilation. After fixing the code to get the native class, NullPointerException went away and the asset loaded as expected.

I have 2 theories about this. And I'm not sure about both of them, because I've only studied how Il2CPP works superficially.

1. Unity does not compile all of its code to CPP at all.
2. Unity cuts out unused methods and classes when compiling to CPP.

Since I tested this on Miside, I can't say for sure that they don't use AssetBundle, but most likely not.

Unity cuts out unused methods and classes when compiling to CPP.

This is what's happening. It's called stripping. We unstrip Unity modules in the later passes of generation.

Unity cuts out unused methods and classes when compiling to CPP.

This is what's happening. It's called stripping. We unstrip Unity modules in the later passes of generation.

In that case, there is no pointer to the IL2CPP class for AssetBundle because it is an unstripped type, right? Or have I misunderstood how this works? A little later I will check how it works if the class is used directly in the game assembly

The only thing that confuses me is GC Finalize. Could you please tell me how it works? I'm not sure AssetBundle shouldn't have it.