Search Unity

Unity 2018.1.0f2 - build fails

Discussion in 'Unity Build Automation' started by SniperED007, May 3, 2018.

  1. SniperED007

    SniperED007

    Joined:
    Sep 29, 2013
    Posts:
    345
    Since upgrading to Unity 2018.1 the cloud builds fail with this:

    404: [Unity] EXCEPTION: ArgumentException: parsing "<key>DeveloperCertificates<\/key>[
    405: [Unity] UnityEditor.CloudBuild.BuildLogger:HighlightUnityErrors(String, String, LogType)
    406: [Unity] ArgumentException: parsing "<key>DeveloperCertificates<\/key>[
    407: [Unity] Finished exporting player successfully.
    408: [Unity] EXCEPTION: DirectoryNotFoundException: Could not find a part of the path.........
    409: [Unity] UnityEditor.CloudBuild.BuildLogger:HighlightUnityErrors(String, String, LogType)
    410: [Unity] DirectoryNotFoundException: Could not find a part of the path "/BUILD_PATH/..............
    411: [Unity] ERROR: executeMethod method UnityEditor.CloudBuild.Builder.Build threw exception.
    412: [Unity] UnityEditor.CloudBuild.BuildLogger:HighlightUnityErrors(String, String, LogType)
    413: ! build of 'default-ios' failed. compile failed
    414: publishing finished successfully.
    415: Finished: FAILURE
     
  2. HaakonL

    HaakonL

    Joined:
    Mar 13, 2014
    Posts:
    123
    Failing here as well:

    40178: [Unity] EXCEPTION: DirectoryNotFoundException: Could not find a part of the path "/BUILD_PATH/monkeybin.board-rush.ios/temp.XXXXXX20180503-5852-qcjo7l/Unity-iPhone.xcodeproj/project.pbxproj".
    40179: [Unity] UnityEngine.DebugLogHandler:Internal_Log(LogType, String, Object)
    40180: [Unity] UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
    40181: [Unity] UnityEngine.Logger:Log(LogType, Object)
    40182: [Unity] UnityEngine.Debug:Log(Object)
    40183: [Unity] UnityEditor.CloudBuild.BuildLogger:Log(String)
    40184: [Unity] UnityEditor.CloudBuild.BuildLogger:HighlightUnityErrors(String, String, LogType)
    40185: [Unity] DirectoryNotFoundException: Could not find a part of the path "/BUILD_PATH/monkeybin.board-rush.ios/temp.XXXXXX20180503-5852-qcjo7l/Unity-iPhone.xcodeproj/project.pbxproj".
    40186: [Unity] at (wrapper remoting-invoke-with-check) System.IO.FileStream..ctor(string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare,int,System.IO.FileOptions,string,bool,bool,bool)
    40187: [Unity] at (wrapper remoting-invoke-with-check) System.IO.StreamReader..ctor(string)
    40188: [Unity] at UnityEditor.CloudBuild.UnityReflector.FixupXcodeProject (System.String path) [0x00120] in <4f8c6c7d6ef34d799b7de5eb3f4853a8>:0
    40189: [Unity] at UnityEditor.CloudBuild.Builder.FixupXcodeProject (System.String path) [0x00021] in <4f8c6c7d6ef34d799b7de5eb3f4853a8>:0
    40190: [Unity] at UnityEditor.CloudBuild.Builder.Build () [0x0034a] in <4f8c6c7d6ef34d799b7de5eb3f4853a8>:0
    40191: [Unity] ERROR: executeMethod method UnityEditor.CloudBuild.Builder.Build threw exception.
    40192: [Unity] UnityEngine.DebugLogHandler:Internal_Log(LogType, String, Object)
    40193: [Unity] UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
    40194: [Unity] UnityEngine.Logger:Log(LogType, Object)
    40195: [Unity] UnityEngine.Debug:Log(Object)
    40196: [Unity] UnityEditor.CloudBuild.BuildLogger:Log(String)
    40197: [Unity] UnityEditor.CloudBuild.BuildLogger:HighlightUnityErrors(String, String, LogType)
    40198: [Unity] executeMethod method UnityEditor.CloudBuild.Builder.Build threw exception.
    40199: [Unity] Aborting batchmode due to failure:
    40200: [Unity] executeMethod method UnityEditor.CloudBuild.Builder.Build threw exception.
    40201: ! Unity player export failed!
    40202: [Unity Package Manager (Upm)]
    40203: Parent process [7604] was terminated
    40204: ! build of 'ios' failed. compile failed
    40205: Publishing build 287 of monkeybin/board-rush for target 'ios'...
    40206: Uploading extra_data/artifacts/icon.png ...done
    40207: Uploading extra_data/build_report/files.json ...done
    40208: Uploading extra_data/build_report/files.reflected.json ...done
    40209: Uploading extra_data/build_report/steps.json ...done
    40210: Uploading extra_data/build_report/steps.reflected.json ...done
    40211: Uploading extra_data/build_report/strippingInfo.json ...done
    40212: Uploading extra_data/build_report/summary.json ...done
    40213: Uploading extra_data/build_report/summary.reflected.json ...done
    40214: publishing finished successfully.
    40215: uninstalling iOS credentials for monkeybin/board-rush - ios
    40216: MAC verified OK
    40217: Removing certificate...
    40218: removing: /BUILD_PATH/Library/MobileDevice/Provisioning Profiles/dca7f63a-e47c-49bc-89da-bfe2c68776c9.mobileprovision
    40219: Storing CACHE_PATH to cache key library_2018_1_0f2
    40220: done.
    40221: Build step 'Execute shell' marked build as failure
    40222: postbuildstatus finished successfully.
    40223: Finished: FAILURE
     
  3. HaakonL

    HaakonL

    Joined:
    Mar 13, 2014
    Posts:
    123
    Sniper, according to a sticky thread in this forum group, you can search for BuildPipeline:BuildPlayerInternalNoCheck in the Full log.

    Sticky thread: https://forum.unity.com/threads/ucb-team-build-failures-with-no-indicated-errors-in-log.437392/

    I did the search in the full log, and found that there is a problem with a regex that is the actual cause of the failure:

    [Unity] EXCEPTION: ArgumentException: parsing "<key>DeveloperCertificates<\/key>[

    When googling the exception I found this:

    https://answers.unity.com/questions/1500884/ios-cloud-build-is-failing-in-201810f1-developerce.html

    And when checking with Cloud Build support team I got confirmed that it is indeed a known issue, and we should use 2018.1.0b9 until they have a fix out.

    When the bug is so clear, I am surprised it was not fixed before releasing f2. At least they could have made the f2 build option unavailable in the cloud build settings...
     
    Deleted User likes this.
  4. any_user

    any_user

    Joined:
    Oct 19, 2008
    Posts:
    374
    We're having the same issue. iOS cloud builds stopped to work after updating to 2018.1. All other builds work fine. Is there any news about this?
     
  5. SniperED007

    SniperED007

    Joined:
    Sep 29, 2013
    Posts:
    345
    Still nothing??

    Tested on 2018.1.1f1
     
  6. Deleted User

    Deleted User

    Guest

    I wish there’d been an official notice about this somewhere, like in the release notes Known Issues or a sticky thread here.
     
  7. HaakonL

    HaakonL

    Joined:
    Mar 13, 2014
    Posts:
    123
    I got an email from Unity saying the fix will be out in the next patch. This was 3 days before 1f1 was released. Just tested 1f1 and the fix is not there. Guess that means we have to wait for a patch.

    We haven't been able to build using a stable version since 2018 came out, which means 3, almost 4 weeks and counting. This bug should never have been released in the first place; It was reported before the official 2018 release, and all it took for Unity to find the bug themselves was some proper Cloud Build QA. Actually as simple as building using a provisioning profile. It just shows how little some of the people at Unity care.
     
    Deleted User likes this.
  8. CerberusInteractive-Morgan

    CerberusInteractive-Morgan

    Joined:
    Aug 25, 2016
    Posts:
    19
    I am experiencing this as well ): Using 2018.2 beta on cloud build seems to work. I would like to use the same version I am working with though.
     
  9. Deleted User

    Deleted User

    Guest

    I get the impression that the QA process for releases is not well coordinated with Unity services. There were also problems with Unity Ads and the 2018.1 release. And since they have apps on the App Store and Google Play, they could rebuild and submit those apps with every new Unity release (like I try to do with mine). All those automated tests are nice, but it’s not a substitute for actual usage.

     
  10. mjirby_mcs

    mjirby_mcs

    Joined:
    Dec 28, 2015
    Posts:
    2
    FYI... Unity 2018.1.2 fixes the issue in CloudBuild.
     
    Deleted User likes this.
  11. SniperED007

    SniperED007

    Joined:
    Sep 29, 2013
    Posts:
    345
    I now get this error with 2018.1.2f1 (only on iOS, the Android build still works fine)

    221: + Building with Xcode 9.3
    222: ▸ ❌; /BUILD_PATH/lighthouse-games-studio.greedcity.default-ios/temp.XXXXXX20180528-5480-rn1lh4/Classes/Unity/UnityInterface.h:187:1: unknown type name 'bool'
    223: ❌; /BUILD_PATH/lighthouse-games-studio.greedcity.default-ios/temp.XXXXXX20180528-5480-rn1lh4/Classes/Unity/UnityInterface.h:187:1: unknown type name 'bool'
    224: ▸ /BUILD_PATH/lighthouse-games-studio.greedcity.default-ios/temp.XXXXXX20180528-5480-rn1lh4/Classes/Unity/UnityInterface.h:187:1: error: unknown type name 'bool'
    225: ▸ 1 error generated.
    226: fastlane finished with errors
    227: /BUILD_PATH/.mason/buildpacks/xcode/bin/compile:253:in `block in build': ! xcode build failed. (RuntimeError)
    228: ! build of 'default-ios' failed. compile failed
     
  12. Nexus1216

    Nexus1216

    Joined:
    Nov 15, 2015
    Posts:
    6

    I'm getting the same error (only in IOS. Android still works fine)
     
  13. SniperED007

    SniperED007

    Joined:
    Sep 29, 2013
    Posts:
    345
    any news on this?
     
  14. Nexus1216

    Nexus1216

    Joined:
    Nov 15, 2015
    Posts:
    6
    nope. not yet
     
  15. Tagazou

    Tagazou

    Joined:
    Mar 27, 2017
    Posts:
    3
    I've the same "DirectoryNotFoundException: Could not find a part of the path" error using Unity 2018.2.17f1.
    Everything was fine with 2018.2.15f1