Known Issues (and fixes) - February 2017

Here is a list of the issues we’re currently aware of with Unity Cloud Build. If you don’t see your issue here, feel free to make a new thread after reading these helpful posting rules: https://forum.unity3d.com/threads/read-this-before-posting.444938/

As updates are available regarding these issues, we will update this thread as well as those relevant to the issue at hand.

Fixes:

• Shader compiler!*
  • *almost. Our hardware has been streamlined and we have managed to reduce the frequency of these errors significantly. There are further upgrade plans in progress which should eradicate the errors completely, and we will keep you posted on that.
• SVN E200015: authentication failed (seemed to be affecting SVN repos with non-unicode passwords)
  
• Huge log files due to UnityIconDumper:ScaleTexture2D
• Changes to Advanced Options not saving
• Assembla SVN connection issues, SVN workspace is too old error
  • We’ve been working on a fix for these issues and it has been proving successful, so we will start rolling out this fix gradually.
  • If you're experiencing checkout issues, please send us a ticket at http://support.unity3d.com
• Unable to add new build target when using Mercurial

Known Issues:

• Shader unsupported: pass has no vertex shader
  • "Shader Unsupported: '<INSERTSHADERNAMEHERE>' - Pass '<PASSNAMEHERE>' has no vertex shader"
  • Forum post: https://forum.unity3d.com/threads/u...ported-pass-pass-has-no-vertex-shader.444058/
• Perforce creates a new workspace for every build
• Unable to add new build target when using Mercurial

 

Apologies for being slow with posting a March thread. It will be on it's way soon