IL2CPP Cloud Builds failing

Hi,

We've recently switched our backend to use IL2CPP and now our Cloud builds appear to fail. We've tried with Unity 2018.1 and Unity 2018.2, building Standalone Windows 64 builds.

With Unity 2018.1 we get a DirectoryNotFound exception pointing to IL2CPP directories.

With Unity 2018.2 we are getting this error:

525: [Unity] ERROR: Error building Player: Currently selected scripting backend (IL2CPP) is not installed.
526: [Unity] UnityEditor.CloudBuild.BuildLogger:HighlightUnityErrors(String, String, LogType)
527: [Unity] Error building Player: Currently selected scripting backend (IL2CPP) is not installed.

Any ideas? I looked in the config settings and did some searching online and I couldn't find any resolution.

Thanks,
Sam

 

I've had this same error as well; it looks like to me that the Unity Cloud Build servers don't have the player support installed for il2CPP for windows builds.

 

Same here.

 

This is still an issue. Is this going to be fixed anytime soon? Also linux il2cpp isn't supported either.

245: [Unity] ERROR: Error building Player: Currently selected scripting backend (IL2CPP) is not installed.
246: [Unity] Error building Player: Currently selected scripting backend (IL2CPP) is not installed.

 

Also happens to me on windows standalone. Waiting for this support

 

Has it been fixed?

 

any info about progress?

 

Unfortunately, we're still getting this error. Happens only on Win64 in our case. Android and Mac are working perfectly fine.

 

Yep, we too got this error today on Win64. Mac build's working.

 

Is there any update on when this support will be coming?

 

April 15th and still no support. Any update on this @ollieblanks ?

 

Looks like I'm in the same boat. Could really use the backend due to performance and security reasons.

 

Any updates on this issue?

 

Bump

 

Still not working with Unity 2019.1.5f. That makes IL2CPP unusable in any real-world project unless you want to maintain two separate build servers.

 

Waiting for this for a year now. Hope it will be available soon - as currently Cloud Build is unfortunately useless for us

 

This is just a regular reminder that IL2CPP support is still missing. It's really a shame - it is supposed to be the best compilation method in Unity / producing the fastest binaries, but it not supported by the official build infrastructure.

 

Is there a workaround that will let you easily tell the build to use Mono on Windows builds but keep IL2CPP for macOS etc. for now that's not too hacky? (What constitutes hacky is left as an exercise for the reader...)

 

You can use PlayerSettings.SetScriptingBackend in a Pre-Export Method to achieve this.

 

Which is recommended nowadays instead, Mono2x or WinRTDotNet? I'd guess Mono2x...?

 

Yeah it will be Mono2x - I didn't realize we actually still had any support for WinRT and I'm guessing that support is only partial at best.

 

Cool, working now. For future reference, here's the code I'm using and the config in Unity Cloud for my Windows build to make it work.

Code (CSharp):

1.  
2. using UnityEngine;
3.  
4. public class BuildConfiguration
5. {
6.     public static void PreExport()
7.     {
8.         string status = "Default";
9.  
10. #if UNITY_CLOUD_BUILD
11.         PlayerSettings.SetScriptingBackend(BuildTargetGroup.Standalone, ScriptingImplementation.Mono2x);
12.         status = "Customized To Use Mono";
13. #endif
14.         Debug.Log($"Build Configuration - {status}");
15.     }
16. }

Thanks!

 

We now have the ability to try out building Windows Standalone with IL2CPP. We're looking for anyone interested in trying out out: https://forum.unity.com/threads/survey-windows-builders.923450/

 

so... does this work yet?

 

I too would like to know when this will work!

 

Hi. I'm very interested in this as well. May I ask what's the status of IL2CPP builds on UCB?
- Are Linux / Mac supported for IL2CPP on UCB?
- I see Windows builds are not supported still in UCB
- When, approximately may we expect this?

Thank you!
Charles

 

I'm still running into this same issue at the end of October 2021, 4 months after the Windows Builders announcement... is there an option somewhere where we choose to opt-in into the windows servers, or at least make sure they are actually being used?

Also, the Mac target is failing for IL2CPP because it requires Xcode 12.2 but 10.15.4 is the one in use.. it would be nice to have an option to choose the Xcode version from a dropdown, like you have for the iOS target.

 

I see an option to opt-out of the Windows Builders, but it's the other way around, I want to make sure I *am* using the Windows Builders, so that I can build with IL2CPP on Windows and Linux (which seems to not be possible atm, even though I have "Disable Windows Builders" unchecked in the target's advanced settings).

Regarding the Xcode version, we can choose the Xcode version for iOS builds, but I was referring to MacOS builds, which do not have any "Signing Credentials" tab, nor does it have an Xcode option anywhere I could find.