Search Unity

Official XCode 13.3.1, 13.4.0, 13.4.1, and 14 RC experimental release

Discussion in 'Unity Build Automation' started by Max_F_Unity, Aug 8, 2022.

  1. Max_F_Unity

    Max_F_Unity

    Unity Technologies

    Joined:
    May 12, 2022
    Posts:
    13
    We sincerely apologize for the unexpected delay in launching XCode 13.3.1 due to several unforeseen issues. We understand that having the latest XCode version is critical to your success. We’ve been working hard to support version 13.3.1 of XCode for the past months. Still, given the nature and diversity of projects built using Unity Cloud Build, we prefer to release XCode 13.3.1 under the experimental label for a few weeks before setting the majority of the users to use this version automatically. That’s why we decided to release Xcode 13.3.1 under an "experimental" label for a few weeks. This will enable you to build projects needing this version and help us prove it stable before the general availability.

    To use this experimental version, you need to specifically select it as your XCode version, as the “Use Latest Compatible Version” option will set the latest stable version. Also, when the experimental label is removed, your build targets using “XCode 13.3.1 (Experimental)” will keep using the stable “XCode 13.3.1” version and not the “Latest Compatible Version”. If you decided to use this version and ran into any problems, we’d appreciate it if you could raise the matter with our support team. While we aim to prioritize all the issues that might occur with this version to improve the stability of our platform continuously, this is still an experimental release, and we can not guarantee quick resolution times. You can always switch back to one of the stable XCode versions during this time. Finally, not all our builders are equipped with this version, so you may experience queuing even if you have available concurrency.

    Once again, we totally understand that our delay in releasing the latest XCode versions is far below what you deserve. That’s why we have started several initiatives this year to streamline supporting OS version, Xcode, and Android SDK releases. Our goal by the end of the year is to establish technology and processes that enable us to support these dependencies within three months after their release.

    Thank you,
    Cloud Build team

    Update (August 11, 2022):
    XCode 13.4.0 is also now available under an "experimental" label.

    Update (September 21, 2022):
    XCode versions 13.4.1 and 14 RC are also now available under an "experimental" label.
     
    Last edited: Sep 21, 2022
    rajantande likes this.
  2. jimmying

    jimmying

    Joined:
    Sep 20, 2017
    Posts:
    107
    Anyone else having issues? My build was successful, but I'm unable to get a share link. But the build time was abnormally quick -- 7 mins as opposed to around an hour.

    Also, unrelated, but about 6 of my last builds (Android builds) are showing incorrect build times.

    Have submitted a support ticket.
     
  3. unityventures7

    unityventures7

    Joined:
    Mar 19, 2020
    Posts:
    13
    Here's the issue with the experimental we are having


    14152: 2022-08-08 15:58:43.620 xcodebuild[14104:37011] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
    14153: 2022-08-08 15:58:43.621 xcodebuild[14104:37011] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
    14154: error: exportArchive: IPA processing failed
    14155: Error Domain=IDEFoundationErrorDomain Code=1 "IPA processing failed" UserInfo={NSLocalizedDescription=IPA processing failed}
    14156: ** EXPORT FAILED **
    14157: Exit status: 70
    14158: +---------------+-------------------------------+
    14159: | Build environment |
    14160: +---------------+-------------------------------+
    14161: | xcode_path | /APPLICATION_PATH/Xcode13_3_1.app |
    14162: | gym_version | 2.207.0 |
    14163: | export_method | development |
    14164: | sdk | iPhoneOS15.4.sdk |
    14165: +---------------+-------------------------------+
     
  4. richardos24

    richardos24

    Joined:
    Jan 27, 2020
    Posts:
    3
    I have the same issue today, cant download my .apk file despite successful build. There are no artifacts.
     
  5. ketuka

    ketuka

    Joined:
    Nov 1, 2021
    Posts:
    15
    upload_2022-8-9_16-19-23.png

    Could this error be caused by the experimental version?
     
    Tommy-Angelo likes this.
  6. Benjamin-Gooding

    Benjamin-Gooding

    Unity Technologies

    Joined:
    Apr 12, 2022
    Posts:
    303
    Opening up a support ticket is the best way for us to get more detailed information on your builds so we can dive in and diagnose the problems and determine if it is related to Monterey, the Editor, or UCB. https://support.unity.com/hc/en-us/requests/new?ticket_form_id=65905

    We are aware of a potential bdsthread_register error. It may appear something like:
    Running script 'Unity Process symbols'
    ❌; fatal error: runtime: bsdthread_register error
    We believe this is related to a MacOS12 BSD Thread Register Issue stemming from the use of GoLang in the Unity Editor. We are looking into this known issue to determine a solution.
     
  7. PeachyPixels

    PeachyPixels

    Joined:
    Feb 17, 2018
    Posts:
    713
    I won't be switching to 13.3.1 anytime soon, but just tested a beta config for one of my apps to help out.

    The build says Success, but no success E-mail was sent. Upon looking at the logs in more detail, the end result also says Success but I see my PostExport script failing with the following...

    Could not find file "/BUILD_PATH/<game-name>.ios-beta-1/temp20220809-6426-ktuy67/Info.plist

    So...

    1. The build says it succeeded, when it didn't.
    2. No E-mail was sent (success or failure)
    3. Info.plist doesn't look like it was generated (for whatever reason, maybe the temp folder is wrong?)
    4. The file name indicates build number 1 when in-fact it was 50

    I'm sticking with 13.2.1 for a while yet, but I hope this helps.
     
  8. Benjamin-Gooding

    Benjamin-Gooding

    Unity Technologies

    Joined:
    Apr 12, 2022
    Posts:
    303
    During the recent UI update, when using Addressables, the default selection was changed to do a "Content Only Build". This results in the build not creating an export. We have brought this to the attention of the Web development team and they are going to go through and create an update to resolve this as that shouldn't be the default.

    In the mean-time, if you are using addressables go into the target's advanced settings and uncheck the "Content Only Build" checkbox (unless that is what you want). By disabling "Content Only Builds" an export will be created for your build.
     
  9. unityventures7

    unityventures7

    Joined:
    Mar 19, 2020
    Posts:
    13
    @benjamingooding trying to open a support ticket with the issue, but it only shows "non techinical issues" as topic available and tell us to come to forum or unity answers:/
     
    masterton likes this.
  10. Benjamin-Gooding

    Benjamin-Gooding

    Unity Technologies

    Joined:
    Apr 12, 2022
    Posts:
    303
    Shoot me a direct message with the name of your build target and the project id as pulled from the dashboard url. I'll take a look at it in the morning.
     
    scotth-unity likes this.
  11. Benjamin-Gooding

    Benjamin-Gooding

    Unity Technologies

    Joined:
    Apr 12, 2022
    Posts:
    303
    I reached out to our Cloud Diagnostics team and this issue is related to how Monterey interacts with applications built using older version of Go. This is a known issue when a tool written with GoLang was built using a version of Go older than 1.11. The Cloud Diagnostics tool was built using GoLang and older versions of Unity are impacted by this bug.

    The Cloud Diagnostics team released a fix for this and versions of Unity including, or newer than the following should not result in a BSD Thread Error when running on Monterey: 2019.4.25f1, 2020.3.5f1, 2021.2.0a1, and any version of 2022.
     
  12. chad_unity872

    chad_unity872

    Joined:
    Jun 28, 2022
    Posts:
    2
    Yes, I'm also seeing a MacOS build fail after the build but before the notarization step.


    25630: [2022-08-18T04:05:19.789Z] - 6.3.6.2.4.2 - WARN: No provider specified. If your Apple ID account is attached to multiple providers, you will need to specify which provider you intend to submit content to or notarization will fail.

    This is the same configuration that previously worked and the configuration shows the provider selected. Seems like it's not being configured anymore.

    EDIT:
    I don't know if I was using any specific version of XCode, since it's Mac I think it was just default.

    EDIT 2:
    I left my other organization (I am not a critical part of their releases) and my Cloud Build was notarized and produced a release.
     
    Last edited: Aug 18, 2022
  13. PedroDuran

    PedroDuran

    Joined:
    Aug 19, 2014
    Posts:
    32
    Development builds are failing in the project that i'm working on.
    Xcode 13.3.1
    Unity 2020.3.34f1
    Production builds success without any problem. But development fails

    Log:

    23740: [2022-08-27T02:53:08.755Z] - 6.3.10.2.4.2 - INFO: ⚠;️ ld: arm64 function not 4-byte aligned: _unwind_tester from /BUILD_PATH/gamovation.chess-club.ios-dev/temp20220826-5904-1fymgi9/Libraries/libiPhone-lib.a(unwind_test_arm64.o)
    23741:
    23742: [2022-08-27T02:53:08.755Z] - 6.3.10.2.4.2 - INFO: ⚠;️ ld: Could not find or use auto-linked library 'swiftCompatibilityConcurrency'
    23743:
    23744: [2022-08-27T02:53:08.755Z] - 6.3.10.2.4.2 - INFO:
    23745:
    23746: [2022-08-27T02:53:08.755Z] - 6.3.10.2.4.2 - INFO: ❌; ld: symbol(s) not found for architecture arm64
    23747:
    23748: [2022-08-27T02:53:08.755Z] - 6.3.10.2.4.2 - INFO:
    23749:
    23750: [2022-08-27T02:53:08.755Z] - 6.3.10.2.4.2 - INFO:
    23751:
    23752: [2022-08-27T02:53:08.755Z] - 6.3.10.2.4.2 - INFO:
    23753:
    23754: [2022-08-27T02:53:08.755Z] - 6.3.10.2.4.2 - INFO: ❌; clang: error: linker command failed with exit code 1 (use -v to see invocation)
    23755:
     
  14. vTrotta_Ulu

    vTrotta_Ulu

    Joined:
    Aug 6, 2020
    Posts:
    4
    Like many others, we're trying to build using XCode 13.3.1 to use Firebase v9+. (We're using Unity 2021.3.8)

    I did a few tests on UCB and the build seems to have completed correctly with the "experimental" XCode, but our post-build script fails to upload it. From what I currently understand, it seems to be an environment issue with the Transporter app.

    We're uploading to Testflight with that line:
    Code (CSharp):
    1. fastlane pilot upload --changelog "${BUILD_ID}" --apple_id 1234567890 --ipa $UNITY_PLAYER_PATH --api_key_path $FILE
    There is 2 different failures on different attempts:
    269207: Ready to upload new build to TestFlight (App: 1234567890)...
    269208: Going to upload updated app to App Store Connect
    269209: This might take a few minutes. Please don't interrupt the script.
    269210: Transporter transfer failed.
    269211: ERROR ITMS-90206: "Invalid Bundle. The bundle at 'MyApp.app/Frameworks/UnityFramework.framework' contains disallowed file 'Frameworks'."
    269212: [iTMSTransporter] [2022-08-31 07:02:42 PDT] <main> DBG-X: parameter ErrorMessage = ERROR ITMS-90206: "Invalid Bundle. The bundle at 'MyApp.app/Frameworks/UnityFramework.framework' contains disallowed file 'Frameworks'.
    269213: [iTMSTransporter] (1102)
    269214: [iTMSTransporter] [2022-08-31 07:02:42 PDT] <main> ERROR: ERROR ITMS-90206: "Invalid Bundle. The bundle at 'MyApp.app/Frameworks/UnityFramework.framework' contains disallowed file 'Frameworks'."
    269215: [iTMSTransporter] [2022-08-31 07:02:42 PDT] <main> DBG-X: The error code is: 1102
    269216: [iTMSTransporter] [2022-08-31 07:02:42 PDT] <main> INFO: Done performing authentication.
    269217: [iTMSTransporter] Package Summary:
    269218: [iTMSTransporter] 1 package(s) were not uploaded because they had problems:
    269219: [iTMSTransporter] ERROR ITMS-90206: "Invalid Bundle. The bundle at 'MyApp.app/Frameworks/UnityFramework.framework' contains disallowed file 'Frameworks'."
    269220: [iTMSTransporter] [2022-08-31 07:02:43 PDT] <main> DBG-X: Returning 1
    269221: ERROR ITMS-90206: "Invalid Bundle. The bundle at 'MyApp.app/Frameworks/UnityFramework.framework' contains disallowed file 'Frameworks'."
    269222: Return status of iTunes Transporter was 1: ERROR ITMS-90206: "Invalid Bundle. The bundle at 'MyApp.app/Frameworks/UnityFramework.framework' contains disallowed file 'Frameworks'."
    269223: The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.
    269224: [!] Error uploading ipa file:
    269225: [Transporter Error Output]: ERROR ITMS-90206: Invalid Bundle. The bundle at 'MyApp.app/Frameworks/UnityFramework.framework' contains disallowed file 'Frameworks'.
    269226: [Transporter Error Output]: Return status of iTunes Transporter was 1: ERROR ITMS-90206: Invalid Bundle. The bundle at 'MyApp.app/Frameworks/UnityFramework.framework' contains disallowed file 'Frameworks'.
    269227: [Transporter Error Output]: The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.

    Ready to upload new build to TestFlight (App: 1234567890)...
    411401: Going to upload updated app to App Store Connect
    411402: This might take a few minutes. Please don't interrupt the script.
    411403: [iTMSTransporter] [2022-08-30 15:10:58 PDT] <main> ERROR: unsatisfied requirement: com.apple.transporter.softwaresupport
    411404: [iTMSTransporter] [2022-08-30 15:10:58 PDT] <main> ERROR: (&(package=com.apple.transporter.core.api)(version>=1.7.0)(!(version>=2.0.0)))
    411405: [iTMSTransporter] [2022-08-30 15:10:58 PDT] <main> ERROR: unsatisfied requirement: com.apple.transporter.core-transport
    411406: [iTMSTransporter] [2022-08-30 15:10:58 PDT] <main> ERROR: (&(package=com.apple.transporter.core.api)(version>=1.7.0)(!(version>=2.0.0)))
    411407: [iTMSTransporter] [2022-08-30 15:10:58 PDT] <main> ERROR: unsatisfied requirement: com.fasterxml.jackson.core.jackson-databind
    411408: [iTMSTransporter] [2022-08-30 15:10:58 PDT] <main> ERROR: (&(package=com.fasterxml.jackson.core.json)(version>=2.11.0)(!(version>=3.0.0)))
    411409: [iTMSTransporter] [2022-08-30 15:10:58 PDT] <main> ERROR: unsatisfied requirement: com.fasterxml.jackson.dataformat.jackson-dataformat-xml
    411410: [iTMSTransporter] [2022-08-30 15:10:58 PDT] <main> ERROR: (&(package=com.fasterxml.jackson.core.base)(version>=2.11.0)(!(version>=3.0.0)))
    411411: [iTMSTransporter] [2022-08-30 15:10:58 PDT] <main> ERROR: unsatisfied requirement: com.fasterxml.jackson.core.jackson-databind
    411412: [iTMSTransporter] [2022-08-30 15:10:58 PDT] <main> ERROR: (&(package=com.fasterxml.jackson.core.filter)(version>=2.11.0)(!(version>=3.0.0)))
    411413: [iTMSTransporter] [2022-08-30 15:10:58 PDT] <main> ERROR: unsatisfied requirement: com.apple.transporter.cliff
    411414: [iTMSTransporter] [2022-08-30 15:10:58 PDT] <main> ERROR: (&(package=com.apple.transporter.core.util)(version>=1.8.0)(!(version>=2.0.0)))
    411415: [iTMSTransporter] [2022-08-30 15:10:58 PDT] <main> ERROR: unsatisfied requirement: com.apple.transporter.core-transport
    411416: [iTMSTransporter] [2022-08-30 15:10:58 PDT] <main> ERROR: (&(package=com.apple.transporter.core.util)(version>=1.8.0)(!(version>=2.0.0)))
    411417: [iTMSTransporter] [2022-08-30 15:10:58 PDT] <main> ERROR: could not find the service with interface (com.apple.transporter.osgi.TransporterService)
    411418: Unable to download a software component: org.apache.httpcomponents.httpcore/4.4.14
    411419: Unable to download a software component: org.apache.httpcomponents.httpclient/4.5.13
    411420: Unable to download a software component: org.apache.commons.commons-codec/1.15.0
    411421: Unable to download a software component: org.apache.felix.scr/2.1.26
    411422: Unable to download a software component: org.apache.felix.configadmin/1.9.20
    411423: Unable to download a software component: com.apple.transporter.aspera-linux-x64/3.9.1.2020-10-28-1600-EST
    411424: Unable to download a software component: com.apple.transporter.aspera-win-x86/3.9.1.2020-10-28-1600-EST
    411425: Unable to download a software component: com.apple.its.epubtoolkit/2.6.5
    411426: Unable to download a software component: com.apple.transporter.itmstransporter/2.3.0.02
    411427: Unable to download a software component: com.apple.transporter.org.apache.poi-osgi/4.0.1
    411428: Unable to download a software component: com.apple.transporter.aspera-transport/1.2.1
    411429: Unable to download a software component: com.apple.transporter.api/1.9.1
    411430: Unable to download a software component: com.apple.transporter.core/1.9.5
    411431: Unable to download a software component: com.apple.transporter.http-transport/1.4.3
    411432: Unable to download a software component: com.apple.transporter.signiant-transport/1.2.0
    411433: Unable to download a software component: com.fasterxml.jackson.datatype.jackson-datatype-jdk8/2.11.3
    411434: Unable to download a software component: com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.11.3
    411435: Unable to download a software component: com.fasterxml.jackson.datatype.jackson-datatype-jsr310/2.11.3
    411436: Unable to download a software component: com.fasterxml.jackson.core.jackson-core/2.11.3
    411437: Unable to download a software component: com.sun.xml.bind.jaxb-impl/2.3.2
    411438: Unable to download a software component: slf4j.api/1.7.32
    411439: Unable to download a software component: com.fasterxml.woodstox.woodstox-core/6.2.1
    411440: unsatisfied requirement: com.apple.transporter.aspera-macos-arm64
    411441: unsatisfied requirement: com.apple.transporter.softwaresupport
    411442: (&(package=com.apple.transporter.stats.api)(version>=2.0.0)(!(version>=3.0.0)))
    411443: unsatisfied requirement: com.apple.transporter.core-transport
    411444: (&(package=com.apple.transporter.core.log.events)(version>=1.0.0)(!(version>=2.0.0)))
    411445: unsatisfied requirement: com.fasterxml.jackson.dataformat.jackson-dataformat-xml
    411446: (&(package=com.fasterxml.jackson.module.jaxb)(version>=2.11.0)(!(version>=3.0.0)))
    411447: unsatisfied requirement: com.apple.transporter.softwaresupport
    411448: (&(package=com.apple.transporter.core.util)(version>=1.8.0)(!(version>=2.0.0)))
    411449: unsatisfied requirement: com.fasterxml.jackson.dataformat.jackson-dataformat-xml
    411450: (&(package=com.fasterxml.jackson.core.format)(version>=2.11.0)(!(version>=3.0.0)))
    411451: unsatisfied requirement: com.fasterxml.jackson.dataformat.jackson-dataformat-xml
    411452: (&(package=com.fasterxml.jackson.core.type)(version>=2.11.0)(!(version>=3.0.0)))
    411453: unsatisfied requirement: com.fasterxml.jackson.core.jackson-databind
    411454: (&(package=com.fasterxml.jackson.core.format)(version>=2.11.0)(!(version>=3.0.0)))
    411455: unsatisfied requirement: com.fasterxml.jackson.core.jackson-databind
    411456: (&(package=com.fasterxml.jackson.core.exc)(version>=2.11.0)(!(version>=3.0.0)))
    411457: unsatisfied requirement: com.fasterxml.jackson.dataformat.jackson-dataformat-xml
    411458: (&(package=com.fasterxml.jackson.core.util)(version>=2.11.0)(!(version>=3.0.0)))
    411459: unsatisfied requirement: com.fasterxml.jackson.core.jackson-databind
    411460: (&(package=com.fasterxml.jackson.core.base)(version>=2.11.0)(!(version>=3.0.0)))
    411461: unsatisfied requirement: com.fasterxml.jackson.core.jackson-databind
    411462: (&(package=com.fasterxml.jackson.core.type)(version>=2.11.0)(!(version>=3.0.0)))
    411463: unsatisfied requirement: com.apple.transporter.core-transport
    411464: (&(package=com.apple.transporter.core.ws.dto.requests)(version>=1.5.0)(!(version>=2.0.0)))
    411465: unsatisfied requirement: com.fasterxml.jackson.core.jackson-databind
    411466: (&(package=com.fasterxml.jackson.core.util)(version>=2.11.0)(!(version>=3.0.0)))
    411467: unsatisfied requirement: com.apple.transporter.cliff
    411468: (&(package=com.apple.transporter.core.api)(version>=1.7.0)(!(version>=2.0.0)))
    411469: unsatisfied requirement: com.apple.transporter.mediatoolkit
    411470: (package=org.apache.poi)
    411471: unsatisfied requirement: com.fasterxml.jackson.dataformat.jackson-dataformat-xml
    411472: (&(package=com.fasterxml.jackson.core)(version>=2.11.0)(!(version>=3.0.0)))
    411473: unsatisfied requirement: com.fasterxml.jackson.core.jackson-databind
    411474: (&(package=com.fasterxml.jackson.core.io)(version>=2.11.0)(!(version>=3.0.0)))
    411475: unsatisfied requirement: com.fasterxml.jackson.dataformat.jackson-dataformat-xml
    411476: (&(package=com.fasterxml.jackson.core.json)(version>=2.11.0)(!(version>=3.0.0)))
    411477: unsatisfied requirement: com.fasterxml.jackson.dataformat.jackson-dataformat-xml
    411478: (&(package=com.fasterxml.jackson.core.io)(version>=2.11.0)(!(version>=3.0.0)))
    411479: unsatisfied requirement: com.fasterxml.jackson.core.jackson-databind
    411480: (&(package=com.fasterxml.jackson.core)(version>=2.11.0)(!(version>=3.0.0)))
    411481: unsatisfied requirement: com.apple.transporter.core-transport
    411482: (&(package=com.apple.transporter.core.mode)(version>=1.0.0)(!(version>=2.0.0)))
    411483: unsatisfied requirement: com.apple.transporter.softwaresupport
    411484: (&(package=com.apple.transporter.core.api)(version>=1.7.0)(!(version>=2.0.0)))
    411485: unsatisfied requirement: com.apple.transporter.core-transport
    411486: (&(package=com.apple.transporter.core.api)(version>=1.7.0)(!(version>=2.0.0)))
    411487: unsatisfied requirement: com.fasterxml.jackson.core.jackson-databind
    411488: (&(package=com.fasterxml.jackson.core.json)(version>=2.11.0)(!(version>=3.0.0)))
    411489: unsatisfied requirement: com.fasterxml.jackson.dataformat.jackson-dataformat-xml
    411490: (&(package=com.fasterxml.jackson.core.base)(version>=2.11.0)(!(version>=3.0.0)))
    411491: unsatisfied requirement: com.fasterxml.jackson.core.jackson-databind
    411492: (&(package=com.fasterxml.jackson.core.filter)(version>=2.11.0)(!(version>=3.0.0)))
    411493: unsatisfied requirement: com.apple.transporter.cliff
    411494: (&(package=com.apple.transporter.core.util)(version>=1.8.0)(!(version>=2.0.0)))
    411495: unsatisfied requirement: com.apple.transporter.core-transport
    411496: (&(package=com.apple.transporter.core.util)(version>=1.8.0)(!(version>=2.0.0)))
    411497: could not find the service with interface (com.apple.transporter.osgi.TransporterService)
    411498: The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.
     
  15. tts-Unity-01

    tts-Unity-01

    Joined:
    Sep 8, 2022
    Posts:
    1
    Our Xcode Cloud build is stuck on:

    6690: [2022-09-14T16:01:28.853Z] - 6.4.1.2.7.4 - INFO: ▸ Copying /BUILD_PATH/Library/Developer/Xcode/DerivedData/

    on the project i'm working on.

    Xcode 13.3.1
    Unity 2022.1.16f1

    Any way to get it running?
    The project was sucsessfully build under 13.2.1 but i need the bitcode fix in FB9951126.

    "When you target iOS 13.4 and later and enable bitcode, the bitcode segment is now stripped correctly. This fixes a crash that prevented some apps from running in older operating systems (iOS 14 and earlier). (90024354) (FB9951126)"
     
  16. wrossmck-unity

    wrossmck-unity

    Unity Technologies

    Joined:
    Nov 9, 2021
    Posts:
    106
    Hey @vTrotta_Ulu, that iTMSTransporter failure is a failure reported by apple via fastlane. if you search the output error code (ERROR ITMS-90206) you will find that there is an error in your project's configuration https://stackoverflow.com/a/49705670/2046648 hope that helps!
     
  17. vTrotta_Ulu

    vTrotta_Ulu

    Joined:
    Aug 6, 2020
    Posts:
    4
    Thanks @wrossmck-unity , you are right. For lost googlers, it turns out ERROR ITMS-90206 was caused by a bug in v171 of the External Dependency Manager.

    Apart from that, any update on a release date for the "experimental" XCode versions for Unity Cloud Build?
     
  18. Benjamin-Gooding

    Benjamin-Gooding

    Unity Technologies

    Joined:
    Apr 12, 2022
    Posts:
    303
  19. gkatsaros-endlessstudios

    gkatsaros-endlessstudios

    Joined:
    Apr 13, 2022
    Posts:
    10
    @chad_unity872, am I understanding you correctly that you just leaving your Unity Organization somehow got you past the notarization error? I've been experiencing issues with Unity Cloud Build notarization right now and am not finding many resources to help solve them...