I have installed 2020.2b12 WITH IL2CPP build add on, but after installation is completed, I can no longer see IL2CPP being installed.
This is confirmed by going to player setting and set the scripting backend to IL2CPP and the build setting says I need to install one.
One thing I noticed is that the Unity installation felt a bit too long (longer than usual) to complete.
Anyone with the same problem? Is this known issue?
I found the link to the manual il2cpp installation and installed it without problem. So my question now is :
Is this going to be the standard way of installing il2cpp from now on? I kind liked how it was where I select option while I install Unity…
There probably was a download or unzip error that made the module installation fail silently. The hub could use more information for this kind of errors. I don’t believe it’s an intended change.
My installation worked fine.
Weird. I tried 3 times and they all failed. Installing them separately did work. Oh well, I will wait for v13 to see what happens.
Sounds like a Hub-related bug to me. Does it happen only with this specific version?
Yeah only with b12
Just to note, that this issue has happened for me on completely different PC as well.
Which exact component combo did you install?
Installed Unity using hub with il2cpp option checked as usual. And then it took very long time for it to finish. When it finished, il2cpp was not installed so I went to the beta page and installed the il2cpp component manually.
Hi @castor76 ,
What’s the last beta version you had before? Is b12 the first one with this issue? If you didn’t try b11 yet, could you please check whether that works? Just trying to pinpoint when this started to happen.
Hello @castor76 ,
Can you specify which IL2CPP module you are installing ? (Mac Build Support or Linux Build Support) ?
And can you check these destinations in your installs to make sure if the module is there and not being read by the editor or it’s just the install that’s failing :
linux-il2cpp : "{UNITY_PATH}/PlaybackEngines/LinuxStandaloneSupport"
mac-il2cpp : "{UNITY_PATH}/Unity.app/Contents/PlaybackEngines/MacStandaloneSupport"
If the module is there, then it’s a problem with the editor detecting the module but if not, we may need your logs to investigate on why the module installs are failing. Thanks for your collaboration and sorry for the inconvenience this is causing you !
B12 is the first time this is starting to happen. I used ALL previous betas before and they all installed IL2CPP without any problems.
As I have stated above, I am just installing Windows versions of Unity 2020.2b12 and Windows IL2CPP module.
I have to uninstall the Unity and try to install it again. 
But it takes so long to do it. A Lot longer than usual. So maybe it has to do with installation.
Also… This is not directly related to the issue, but because I like Unity’s attention, I have submitted a bug report for IL2CPP build failing on 14th of Nov it is still open and not being looked yet 
Just a friendly reminder… haha
I am installing b13, but it “seems” like it is taking very long time again, so I am thinking, where to find the log for the installation process so I can post it here?
Still installing. Downloading part was quick. Just installation part is taking very long time. Almost an hour now.
Ok After installation is completed, here is what I see. :
Also
Nothing…
Indicating that there is error while installing Unity.
Tried to force close hub again. This time it worked.
Runs hub again, now I see the b13 being added. But without Il2cpp option
My guess is that this is hub related, because there could been hub update in between going from b11 to b12… since b13 also happens.
So it could be hub or something from b12 ?
