Unity Cloud Build - "Error: Failed to check out" for iOS build with SVN repository

Unity Services
1

Hi!

I’m trying to make a build for iOS using Unity Cloud Build but I always receive the following messages!

1: Running Prebuild steps 2: Removing bvr 3: Successfully uninstalled bvr-0.2.47 4: Building native extensions. This could take a while… 5: done. 6: bvr 1.2.10 7: bvr-api 0.2.3 8: Checking out a fresh workspace because there’s no workspace at /BUILD_PATH/xxx.default-ios 9: Cleaning local Directory . 10: Checking out https://xxx.svn.cloudforge.com/xxx/xxx/xxx/xxxat revision ‘2016-05-09T21:31:17.997 +0100’ 11: ERROR: Failed to check outhttps://xxx.svn.cloudforge.com/xxx/xxx/xxx/xxx 12: svn: E175002: OPTIONS request failed on ‘/xxx/xxx/trunk/xxx’ 13: Caused by: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure 14: Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure 15: Caused by: java.io.IOException: Failed to check outhttps://xxx.svn.cloudforge.com/xxx/xxx/xxx/xxx 16: svn: E175002: OPTIONS request failed on ‘/xxx/xxx/xxx/xxx’ 17: Caused by: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure 18: Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure 19: postbuildstatus finished successfully. 20: Finished: FAILURE

Does anyone know how can I solve this??? Android build just works fine.
Some additional info:
Unity Version: Unity 5.3.4f1
Auto-Build: false
Xcode Version: Xcode 7.2

2

Are you using an outside service for your SVN hosting? I am and getting this same error… for, like the last week or so.

3

Hey, we fixed that error. We just don’t know exactly what solved it, lol. LOOKS like what was causing it was some configurations in Unity Cloud Build like Unity version along with Xcode version. These were the only changes that we’ve made.

4

Hello,

Just as a heads up, there were changes to handle SSL SVN connections that likely solved this issue. Users should be aware that when using HTTPS SVN, the server name configured in the web server must match the name specified on the SSL certificate for the server (i.e., do not use the local hostname of the server).

5

I’m not sure what that means, but I’ve been getting successful builds again for a bast week or so… so… um… thanks?