For now, users that are dependent on using symlinks should continue to opt-out of the new windows builder infrastructure. It is suggested to avoid using symlinks in Unity projects and replacing them with the source directory itself wherever possible. The type or namespace name 'LitJson' could not be found (are you missing a using directive or an assembly reference?) Our Windows machines are running in a Cygwin environment and as of now may not be able to properly handle these cases resulting in a message similar to the following: This problem seems to occur for nested libraries either through symlinks or git submodules. Some users that are using symlinks or git submodules have reported running into namespace issues.

Platform-Specific Custom Scriptsįor more information regarding platform-specific custom scripts please see this page. We will continue to update this section as we discover new common issues. This goal of this section is to provide some solutions to known problems that can occur as a result of these new infrastructure changes.

Though we are taking action to prevent and fix as many of these issues as possible, there are some things that we cannot fix directly. Windows Builder Transition Common IssuesĪs we transition to our new Windows build machine infrastructure, you may experience some new issues with your builds. Given the scalability of this infrastructure, we anticipate faster build times as well in the near future. This will enable Windows IL2CPP and lower queue times for your builds. As part of our efforts to improve the performance of Cloud Build, we’re beginning the process of shifting our Windows and Android builders to native Windows VMs.

Can unity cloud build make final build