Search Unity

Bug iOS Failed to Archive on Xcode 14.1 & 14.2

Discussion in 'Unity Build Automation' started by GastonC, Mar 23, 2023.

  1. GastonC

    GastonC

    Joined:
    Aug 26, 2012
    Posts:
    38
    Hello! Im trying to build my iOS game with an Xcode 14.1+, to comply with iOS newest deadline.
    The UCB builds are currently working with Xcode 13.4.1 and we are using Unity 2021.3.21f1.
    We tried to build & archive locally with both Xcode 14.1 & 14.2, and it did work, so it makes me think it's something to do with UCB itself.

    Attached is the full log, and some screenshots of the issue.
    We have a hard deadline on April 1st, and this is a live project, so any help is very much appreciated! upload_2023-3-23_18-49-51.png upload_2023-3-23_18-50-7.png upload_2023-3-23_18-50-27.png upload_2023-3-23_18-50-44.png
     

    Attached Files:

    JosephApex likes this.
  2. JosephApex

    JosephApex

    Joined:
    Jan 13, 2021
    Posts:
    9
    My project is having a similar issue as well. Can compile just fine with older xcode versions and local but it fails in cloud builds. Currently using unity 2020.2.1f1 and xcode 13.0.0. Trying yo change it to xcode 14.1 to comply as well.
     
  3. GastonC

    GastonC

    Joined:
    Aug 26, 2012
    Posts:
    38
    Yea, I imagine this is more a UCB issue than an us issue. Lets hope we can get an answer before the deadline
     
  4. JosephApex

    JosephApex

    Joined:
    Jan 13, 2021
    Posts:
    9
    After running more test I think there is something wrong with cloud build. I have two configurations with the exact same settings with the only difference being an environment variable for post build scripts. Even rerunning the old branch the build is now failing even though it had previously worked just fine the previous day. I'll be looking into trying to find a possible fix and will update if I find anything.
     
  5. MasahikoHagio

    MasahikoHagio

    Joined:
    Oct 15, 2021
    Posts:
    7
    me to. fastlane issue?

    Code (JavaScript):
    1. [2023-03-26T15:59:08.732Z] - 7.3.2.2.4.2 - INFO: ** ARCHIVE FAILED **
    2. [2023-03-26T15:59:08.732Z] - 7.3.2.2.4.2 - INFO: Exit status: 65
    3. [2023-03-26T15:59:08.780Z] - 7.3.2.2.4.2 - INFO:
    4. [2023-03-26T15:59:08.780Z] - 7.3.2.2.4.2 - INFO: Maybe the error shown is caused by using the wrong version of Xcode
    5. [2023-03-26T15:59:08.780Z] - 7.3.2.2.4.2 - INFO: Found multiple versions of Xcode in '/APPLICATION_PATH/'
    6. [2023-03-26T15:59:08.780Z] - 7.3.2.2.4.2 - INFO: Make sure you selected the right version for your project
    7. [2023-03-26T15:59:08.780Z] - 7.3.2.2.4.2 - INFO: This build process was executed using '/APPLICATION_PATH/Xcode14_1_0.app'
    8. [2023-03-26T15:59:08.780Z] - 7.3.2.2.4.2 - INFO: If you want to update your Xcode path, either
    9. [2023-03-26T15:59:08.780Z] - 7.3.2.2.4.2 - INFO:
    10. [2023-03-26T15:59:08.780Z] - 7.3.2.2.4.2 - INFO: - Specify the Xcode version in your Fastfile
    11. [2023-03-26T15:59:08.780Z] - 7.3.2.2.4.2 - INFO: ▸ xcversion(version: "8.1") # Selects Xcode 8.1.0
    12. [2023-03-26T15:59:08.780Z] - 7.3.2.2.4.2 - INFO:
    13. [2023-03-26T15:59:08.781Z] - 7.3.2.2.4.2 - INFO: - Specify an absolute path to your Xcode installation in your Fastfile
    14. [2023-03-26T15:59:08.781Z] - 7.3.2.2.4.2 - INFO: ▸ xcode_select "/APPLICATION_PATH/Xcode8.app"
    15. [2023-03-26T15:59:08.781Z] - 7.3.2.2.4.2 - INFO:
    16. [2023-03-26T15:59:08.781Z] - 7.3.2.2.4.2 - INFO: - Manually update the path using
    17. [2023-03-26T15:59:08.781Z] - 7.3.2.2.4.2 - INFO: ▸ sudo xcode-select -s /APPLICATION_PATH/Xcode.app
     
  6. Benjamin-Gooding

    Benjamin-Gooding

    Unity Technologies

    Joined:
    Apr 12, 2022
    Posts:
    303
    If you are still experiencing this issue please open up a support ticket through the dashboard. Dashboard -> Unity DevOps -> Help & Support -> File a Ticket
     
  7. GastonC

    GastonC

    Joined:
    Aug 26, 2012
    Posts:
    38
    Hello @benjamingooding. Just sent the ticket as you requested.
    Please keep in mind, there is a hard deadline in less than 4 days for this as per Apples requirement.
     
  8. JosephApex

    JosephApex

    Joined:
    Jan 13, 2021
    Posts:
    9
    I have also put in a ticket. I'll leave my most recent error logs in case someone comes along who can help debug.
    Code (JavaScript):
    1. [warning] [2023-03-28T14:34:31.935Z] - 7.3.2.2.7.4 - WARN:        build was signed for app store!
    2. [warning] [2023-03-28T14:34:31.966Z] - 7.3.2.2.7.4 - WARN:        ! Podfile.lock and Pods/ directory exists, skipping cocoapods install
    3. [warning] [2023-03-28T14:34:54.505Z] - 7.3.2.2.7.4 - INFO: ▸     Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'UnityFramework' from project 'Unity-iPhone')
    4. [warning] [2023-03-28T14:34:54.507Z] - 7.3.2.2.7.4 - INFO: ▸     Run script build phase 'Crashlytics Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'UnityFramework' from project 'Unity-iPhone')
    5. [warning] [2023-03-28T14:34:54.507Z] - 7.3.2.2.7.4 - INFO: ▸     Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Libuv-gRPC' from project 'Pods')
    6. [warning] [2023-03-28T14:34:54.507Z] - 7.3.2.2.7.4 - INFO: ▸     Run script build phase 'Crashlytics Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Unity-iPhone' from project 'Unity-iPhone')
    7. [warning] [2023-03-28T14:34:54.507Z] - 7.3.2.2.7.4 - INFO: ▸     Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'abseil' from project 'Pods')
    8. [warning] [2023-03-28T14:34:54.507Z] - 7.3.2.2.7.4 - INFO: ▸     Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'gRPC-Core' from project 'Pods')
    9. [warning] [2023-03-28T14:34:54.508Z] - 7.3.2.2.7.4 - INFO: ▸     Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'gRPC-C++' from project 'Pods')
    10. [warning] [2023-03-28T14:34:54.508Z] - 7.3.2.2.7.4 - INFO: ▸     Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'BoringSSL-GRPC' from project 'Pods')
    11. [warning] [2023-03-28T14:34:54.525Z] - 7.3.2.2.7.4 - INFO:     Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'UnityFramework' from project 'Unity-iPhone')
    12. [warning] [2023-03-28T14:34:54.525Z] - 7.3.2.2.7.4 - INFO:     Run script build phase 'Crashlytics Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'UnityFramework' from project 'Unity-iPhone')
    13. [warning] [2023-03-28T14:34:54.525Z] - 7.3.2.2.7.4 - INFO:     Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Libuv-gRPC' from project 'Pods')
    14. [warning] [2023-03-28T14:34:54.525Z] - 7.3.2.2.7.4 - INFO:     Run script build phase 'Crashlytics Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Unity-iPhone' from project 'Unity-iPhone')
    15. [warning] [2023-03-28T14:34:54.525Z] - 7.3.2.2.7.4 - INFO:     Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'abseil' from project 'Pods')
    16. [warning] [2023-03-28T14:34:54.525Z] - 7.3.2.2.7.4 - INFO:     Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'gRPC-Core' from project 'Pods')
    17. [warning] [2023-03-28T14:34:54.525Z] - 7.3.2.2.7.4 - INFO:     Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'gRPC-C++' from project 'Pods')
    18. [warning] [2023-03-28T14:34:54.525Z] - 7.3.2.2.7.4 - INFO:     Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'BoringSSL-GRPC' from project 'Pods')
    19. [warning] [2023-03-28T14:34:54.542Z] - 7.3.2.2.7.4 - INFO:/BUILD_PATH/apex-innovations.nihss.ios_beta_build/temp20230328-6413-1hie6ry/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.1.99. (in target 'FirebaseInstallations' from project 'Pods')
    20. [warning] [2023-03-28T14:34:54.543Z] - 7.3.2.2.7.4 - INFO:/BUILD_PATH/apex-innovations.nihss.ios_beta_build/temp20230328-6413-1hie6ry/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.1.99. (in target 'gRPC-C++' from project 'Pods')
    21. [warning] [2023-03-28T14:34:54.543Z] - 7.3.2.2.7.4 - INFO: ▸ warning: Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'gRPC-C++' from project 'Pods')
    22. [warning] [2023-03-28T14:34:54.543Z] - 7.3.2.2.7.4 - INFO:/BUILD_PATH/apex-innovations.nihss.ios_beta_build/temp20230328-6413-1hie6ry/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.1.99. (in target 'BoringSSL-GRPC' from project 'Pods')
    23. [warning] [2023-03-28T14:34:54.543Z] - 7.3.2.2.7.4 - INFO: ▸ warning: Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'BoringSSL-GRPC' from project 'Pods')
    24. [error] [2023-03-28T14:34:54.567Z] - 7.3.2.2.7.4 - ERROR: xcode build failed
    25. [error]   RuntimeError (Build Failure):
    26. [error] /BUILD_PATH/.rvm/gems/ruby-2.7.4/gems/bvr-7.3.2.2.7.4/lib/bvr/build/handlers/platform/xcode_compiler.rb:314:in `block in exec_fastlane': Build Failure (RuntimeError)
    27. [error] Finished: FAILURE
     
    Churapps likes this.
  9. Epsilon_Delta

    Epsilon_Delta

    Joined:
    Mar 14, 2018
    Posts:
    258
    We have similar issue, will submit a support ticket.
    Xcode 13.x.x builds fine, changing to 14.x.x. will fail the build

    Code (CSharp):
    1. [error] [2023-03-30T15:43:45.571Z] - 7.3.3.2.7.4 - INFO: ❌  Undefined symbols for architecture arm64
    2. [2023-03-30T15:43:45.572Z] - 7.3.3.2.7.4 - INFO: > Symbol: _$s10Foundation22_convertErrorToNSErrorySo0E0Cs0C0_pF
    3. [2023-03-30T15:43:45.572Z] - 7.3.3.2.7.4 - INFO: > Referenced from: _$s14UnityFramework22FBSDKTournamentUpdaterC6update12tournamentID5score17completionHandlerySS_SiySb_s5Error_pSgtctF048$s10ObjectiveC8ObjCBoolVSo7NSErrorCSgIeyByy_Sbs5K12_pSgIegyg_TR0M1C0oP0VSo0R0CSgIeyByy_Tf1nncn_nTf4nndg_n in FBSDKTournamentUpdater.o
    4. [2023-03-30T15:43:45.572Z] - 7.3.3.2.7.4 - INFO:
    5. [2023-03-30T15:43:45.572Z] - 7.3.3.2.7.4 - INFO:
    6. [2023-03-30T15:43:45.572Z] - 7.3.3.2.7.4 - INFO:
    7. [error] [2023-03-30T15:43:45.572Z] - 7.3.3.2.7.4 - INFO: ❌  ld: symbol(s) not found for architecture arm64
    8. [2023-03-30T15:43:45.572Z] - 7.3.3.2.7.4 - INFO:
    9. [2023-03-30T15:43:45.572Z] - 7.3.3.2.7.4 - INFO:
    10. [2023-03-30T15:43:45.572Z] - 7.3.3.2.7.4 - INFO:
    11. [error] [2023-03-30T15:43:45.572Z] - 7.3.3.2.7.4 - INFO: ❌  clang: error: linker command failed with exit code 1 (use -v to see invocation)
     
  10. unity_CFAF82E201B6814E46FB

    unity_CFAF82E201B6814E46FB

    Joined:
    May 12, 2022
    Posts:
    1
    Hello! Is there any update/fix for this problem?
     
  11. GastonC

    GastonC

    Joined:
    Aug 26, 2012
    Posts:
    38
    Still waiting for one......
     
  12. MasahikoHagio

    MasahikoHagio

    Joined:
    Oct 15, 2021
    Posts:
    7
    I was able to do a local build and create IPA successfully.
    Is the problem a lib that is not included in the custom pod?
    So, my main concern is the following, does this affect the build?

    >Run script build phase 'Create Symlinks to Header Folders' .....
     
  13. unity_320AC700C5AB25D195F1

    unity_320AC700C5AB25D195F1

    Joined:
    Nov 19, 2021
    Posts:
    22
    MacOS Monterey 12.6.4
    XCode 14.1
    Unity 2020.3.26f1

    Getting the same issue on our project too, following changes made to migrate to Xcode 14.1. Building iOS target locally works fine for me (after a couple of teething issues; needed to set DEVELOPMENT_TEAM in Pod targets and disable bitcode like so).

    To attempt to remove the 'Based on Dependency Analysis' warnings, I've modified the Podfile in our PostProcessBuild script, following this post https://github.com/CocoaPods/CocoaPods/issues/11444#issuecomment-1300023416

    However, I hit some errors in the Pod syntax so am stuck right now.

    Here are logs from UCB with warnings around point of failure for reference:

    Code (JavaScript):
    1. [2023-04-04T12:15:33.312Z] - 7.3.3.2.7.4 - INFO: ▸ Clean Succeeded
    2. [warning] [2023-04-04T12:15:39.756Z] - 7.3.3.2.7.4 - INFO: ▸     Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'UnityFramework' from project 'Unity-iPhone')
    3. [warning] [2023-04-04T12:15:39.756Z] - 7.3.3.2.7.4 - INFO: ▸     Run script build phase 'Unity Process symbols' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'UnityFramework' from project 'Unity-iPhone')
    4. [warning] [2023-04-04T12:15:39.756Z] - 7.3.3.2.7.4 - INFO: ▸     Run script build phase 'Unity Process symbols' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Unity-iPhone' from project 'Unity-iPhone')
    5. [warning] [2023-04-04T12:15:39.757Z] - 7.3.3.2.7.4 - INFO: ▸     Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'PromisesObjC' from project 'Pods')
    6. [2023-04-04T12:15:39.763Z] - 7.3.3.2.7.4 - INFO:** ARCHIVE FAILED **
    7. [2023-04-04T12:15:39.775Z] - 7.3.3.2.7.4 - INFO: ▸ Clean Succeeded
    8. [warning] [2023-04-04T12:15:39.775Z] - 7.3.3.2.7.4 - INFO:     Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'UnityFramework' from project 'Unity-iPhone')
    9. [warning] [2023-04-04T12:15:39.775Z] - 7.3.3.2.7.4 - INFO:     Run script build phase 'Unity Process symbols' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'UnityFramework' from project 'Unity-iPhone')
    10. [warning] [2023-04-04T12:15:39.775Z] - 7.3.3.2.7.4 - INFO:     Run script build phase 'Unity Process symbols' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Unity-iPhone' from project 'Unity-iPhone')
    11. [warning] [2023-04-04T12:15:39.775Z] - 7.3.3.2.7.4 - INFO:     Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'PromisesObjC' from project 'Pods')
    12. [2023-04-04T12:15:39.775Z] - 7.3.3.2.7.4 - INFO: ** ARCHIVE FAILED **
    13. [2023-04-04T12:15:39.775Z] - 7.3.3.2.7.4 - INFO: Exit status: 65
    14. [2023-04-04T12:15:39.781Z] - 7.3.3.2.7.4 - INFO:
    15. [2023-04-04T12:15:39.781Z] - 7.3.3.2.7.4 - INFO: Maybe the error shown is caused by using the wrong version of Xcode
    16. [2023-04-04T12:15:39.781Z] - 7.3.3.2.7.4 - INFO: Found multiple versions of Xcode in '/APPLICATION_PATH/'
    17. [2023-04-04T12:15:39.781Z] - 7.3.3.2.7.4 - INFO: Make sure you selected the right version for your project
    18. [2023-04-04T12:15:39.781Z] - 7.3.3.2.7.4 - INFO: This build process was executed using '/APPLICATION_PATH/Xcode14_1_0.app'
    19. [2023-04-04T12:15:39.782Z] - 7.3.3.2.7.4 - INFO: If you want to update your Xcode path, either
    20. [2023-04-04T12:15:39.782Z] - 7.3.3.2.7.4 - INFO:
    21. [2023-04-04T12:15:39.782Z] - 7.3.3.2.7.4 - INFO: - Specify the Xcode version in your Fastfile
    22. [2023-04-04T12:15:39.782Z] - 7.3.3.2.7.4 - INFO: ▸ xcversion(version: "8.1") # Selects Xcode 8.1.0
    23. [2023-04-04T12:15:39.782Z] - 7.3.3.2.7.4 - INFO:
    24. [2023-04-04T12:15:39.782Z] - 7.3.3.2.7.4 - INFO: - Specify an absolute path to your Xcode installation in your Fastfile
    25. [2023-04-04T12:15:39.782Z] - 7.3.3.2.7.4 - INFO: ▸ xcode_select "/APPLICATION_PATH/Xcode8.app"
    26. [2023-04-04T12:15:39.782Z] - 7.3.3.2.7.4 - INFO:
    27. [2023-04-04T12:15:39.782Z] - 7.3.3.2.7.4 - INFO: - Manually update the path using
    28. [2023-04-04T12:15:39.782Z] - 7.3.3.2.7.4 - INFO: ▸ sudo xcode-select -s /APPLICATION_PATH/Xcode.app
    29. [2023-04-04T12:15:39.782Z] - 7.3.3.2.7.4 - INFO:
    30. [2023-04-04T12:15:39.787Z] - 7.3.3.2.7.4 - INFO:
    31. [2023-04-04T12:15:39.788Z] - 7.3.3.2.7.4 - INFO: +-------------+-------------------------------+
    32. [2023-04-04T12:15:39.788Z] - 7.3.3.2.7.4 - INFO: |              Build environment              |
    33. [2023-04-04T12:15:39.788Z] - 7.3.3.2.7.4 - INFO: +-------------+-------------------------------+
    34. [2023-04-04T12:15:39.788Z] - 7.3.3.2.7.4 - INFO: | xcode_path  | /APPLICATION_PATH/Xcode14_1_0.app |
    35. [2023-04-04T12:15:39.788Z] - 7.3.3.2.7.4 - INFO: | gym_version | 2.211.0                       |
    36. [2023-04-04T12:15:39.788Z] - 7.3.3.2.7.4 - INFO: | sdk         | iPhoneOS16.1.sdk              |
    37. [2023-04-04T12:15:39.788Z] - 7.3.3.2.7.4 - INFO: +-------------+-------------------------------+
    38. [2023-04-04T12:15:39.788Z] - 7.3.3.2.7.4 - INFO:
    39. [warning] [2023-04-04T12:15:39.789Z] - 7.3.3.2.7.4 - INFO:/BUILD_PATH/treesplease-games.merge1.testing-ios-reviezgth3key/temp20230404-6400-14pqd4n/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.1.99. (in target 'GoogleUtilities' from project 'Pods')
    40. [warning] [2023-04-04T12:15:39.789Z] - 7.3.3.2.7.4 - INFO:/BUILD_PATH/treesplease-games.merge1.testing-ios-reviezgth3key/temp20230404-6400-14pqd4n/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.1.99. (in target 'Firebase' from project 'Pods')
    41. [warning] [2023-04-04T12:15:39.789Z] - 7.3.3.2.7.4 - INFO:/BUILD_PATH/treesplease-games.merge1.testing-ios-reviezgth3key/temp20230404-6400-14pqd4n/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.1.99. (in target 'FirebaseMessaging' from project 'Pods')
    42. [warning] [2023-04-04T12:15:39.789Z] - 7.3.3.2.7.4 - INFO:/BUILD_PATH/treesplease-games.merge1.testing-ios-reviezgth3key/temp20230404-6400-14pqd4n/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.1.99. (in target 'VungleSDK-iOS' from project 'Pods')
    43. [warning] [2023-04-04T12:15:39.789Z] - 7.3.3.2.7.4 - INFO:/BUILD_PATH/treesplease-games.merge1.testing-ios-reviezgth3key/temp20230404-6400-14pqd4n/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.1.99. (in target 'FBSDKGamingServicesKit' from project 'Pods')
    44. [2023-04-04T12:15:39.789Z] - 7.3.3.2.7.4 - INFO:
    45. [2023-04-04T12:15:39.789Z] - 7.3.3.2.7.4 - INFO: ⬆️  Check out the few lines of raw `xcodebuild` output above for potential hints on how to solve this error
    46. [2023-04-04T12:15:39.790Z] - 7.3.3.2.7.4 - INFO:   For the complete and more detailed error log, check the full log at:
    47. [2023-04-04T12:15:39.790Z] - 7.3.3.2.7.4 - INFO:   /BUILD_PATH/Library/Logs/gym/LongleafValley-Unity-iPhone.log
    48. [2023-04-04T12:15:39.790Z] - 7.3.3.2.7.4 - INFO:
    49. [2023-04-04T12:15:39.790Z] - 7.3.3.2.7.4 - INFO: Looks like fastlane ran into a build/archive error with your project
    50. [2023-04-04T12:15:39.790Z] - 7.3.3.2.7.4 - INFO: It's hard to tell what's causing the error, so we wrote some guides on how
    51. [2023-04-04T12:15:39.790Z] - 7.3.3.2.7.4 - INFO: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
    52. [2023-04-04T12:15:39.790Z] - 7.3.3.2.7.4 - INFO: Before submitting an issue on GitHub, please follow the guide above and make
    53. [2023-04-04T12:15:39.790Z] - 7.3.3.2.7.4 - INFO: sure your project is set up correctly.
    54. [2023-04-04T12:15:39.790Z] - 7.3.3.2.7.4 - INFO: fastlane uses `xcodebuild` commands to generate your binary, you can see the
    55. [2023-04-04T12:15:39.790Z] - 7.3.3.2.7.4 - INFO: the full commands printed out in yellow in the above log.
    56. [2023-04-04T12:15:39.790Z] - 7.3.3.2.7.4 - INFO: Make sure to inspect the output above, as usually you'll find more error information there
     
    Last edited: Apr 4, 2023
  14. jlemosz

    jlemosz

    Unity Technologies

    Joined:
    Oct 2, 2020
    Posts:
    9
    Hello everyone,

    Could you check which version of cocoapods you are using locally and install it using the following pre-build script (this example is for version 1.12.0):

    Code (JavaScript):
    1. gem install cocoapods -v 1.12.0
    2. echo "current cocoapods version: "
    3. gem which cocoapods
     
    Last edited: Apr 4, 2023
    vg_swift-games likes this.
  15. MasahikoHagio

    MasahikoHagio

    Joined:
    Oct 15, 2021
    Posts:
    7
    I succeeded.
     
  16. MasahikoHagio

    MasahikoHagio

    Joined:
    Oct 15, 2021
    Posts:
    7
    on cloud build, set Ruby version to Ruby 2.74
    add Pre-build script

    1. gem install cocoapods -v 1.12.0
    2. echo "current cocoapods version: "
    3. gem which cocoapods

     
    jlemosz, vg_swift-games and Churapps like this.
  17. unity_320AC700C5AB25D195F1

    unity_320AC700C5AB25D195F1

    Joined:
    Nov 19, 2021
    Posts:
    22
    I'm just waiting for our UCB builds to complete after making the same change, so will report back soon. Gives me hope that you had success; fingers crossed.

    We already had Ruby set to 2.74 in our configs, which seemed to be required when we upgraded to IronSource SDK 7.2.5.1 and Xcode 13.3.1 (in case that's useful info for anyone else).
     
  18. Revolter

    Revolter

    Joined:
    Mar 15, 2014
    Posts:
    216
  19. unity_320AC700C5AB25D195F1

    unity_320AC700C5AB25D195F1

    Joined:
    Nov 19, 2021
    Posts:
    22
    So, I checked my local Cocoapods version which was 1.11.3. As I mentioned, local builds worked fine so assumed 1.11.3 was safe and so set this version to be installed in a pre-build script using the template code above. However, the build failed with the same warnings appearing, plus this error:

    Code (JavaScript):
    1. error: FBSDKCoreKit-FacebookSDKStrings has conflicting provisioning settings. FBSDKCoreKit-FacebookSDKStrings is automatically signed, but code signing identity Apple Distribution: <SIGNING ID> has been manually specified. Set the code signing identity value to "Apple Development" in the build settings editor, or switch to manual signing in the Signing & Capabilities editor. (in target 'FBSDKCoreKit-FacebookSDKStrings' from project 'Pods')
    I then modified the pre-build script to use 1.12.0 since @MasahikoHagio reported this working and the UCB build succeeded o_O I like to keep local environments on par with UCB for consistency so guess I'll install 1.12.0 but am confused about the differences in build results.
     
    jlemosz likes this.
  20. Revolter

    Revolter

    Joined:
    Mar 15, 2014
    Posts:
    216
    You might need to update Facebook SDK
     
  21. Epsilon_Delta

    Epsilon_Delta

    Joined:
    Mar 14, 2018
    Posts:
    258
  22. Revolter

    Revolter

    Joined:
    Mar 15, 2014
    Posts:
    216
  23. Revolter

    Revolter

    Joined:
    Mar 15, 2014
    Posts:
    216
    Can confirm that this fixed it for me, thanks!
     
    jlemosz and MasahikoHagio like this.
  24. vg_swift-games

    vg_swift-games

    Joined:
    Aug 2, 2021
    Posts:
    26
    Will there be a solution from Unity side that doesn't require the pre-build script?
     
  25. Epsilon_Delta

    Epsilon_Delta

    Joined:
    Mar 14, 2018
    Posts:
    258
    This did not work in my case

    I will get back to this after I resolve cloud build issue, but thanks for letting me know that it's working for you.
     
  26. Benjamin-Gooding

    Benjamin-Gooding

    Unity Technologies

    Joined:
    Apr 12, 2022
    Posts:
    303
    We upgraded the version of Cocoapods being used by Ruby 2.7.4 to 1.12.0 so a pre-build script to update the version of cocoapods is no longer needed.
     
  27. Epsilon_Delta

    Epsilon_Delta

    Joined:
    Mar 14, 2018
    Posts:
    258
    Unfortunately it did not help to resolve my issue, 13.x builds fine, 14.x causes aforementioned error. Also, I can build and archive locally with 14.x even in batch mode
     
    Last edited: Apr 11, 2023
  28. Benjamin-Gooding

    Benjamin-Gooding

    Unity Technologies

    Joined:
    Apr 12, 2022
    Posts:
    303
    Please open up a support ticket via the Unity Dashboard so that one of our support engineers can help take a look
     
  29. Epsilon_Delta

    Epsilon_Delta

    Joined:
    Mar 14, 2018
    Posts:
    258
    I did so a week ago, I just write it here for people who might find it useful/have similar problems. If I resolve this problem I will also write a solution here.
     
  30. MasahikoHagio

    MasahikoHagio

    Joined:
    Oct 15, 2021
    Posts:
    7
    hello
    Looking at your logs, I suspect there may be other issues prior to the xcode14.1 build issue.
     
  31. Epsilon_Delta

    Epsilon_Delta

    Joined:
    Mar 14, 2018
    Posts:
    258
    Can you please be more specific
     
  32. MasahikoHagio

    MasahikoHagio

    Joined:
    Oct 15, 2021
    Posts:
    7
    In your log there exists a linker error. First, I recommend creating an ipa locally to discover the problem.
     
  33. Epsilon_Delta

    Epsilon_Delta

    Joined:
    Mar 14, 2018
    Posts:
    258
    As I wrote, locally I don't have a problem, I can build and archive, only cloudbuild fails
     
  34. unity_320AC700C5AB25D195F1

    unity_320AC700C5AB25D195F1

    Joined:
    Nov 19, 2021
    Posts:
    22
    Just to loop back on my last comment here, I went down a rabbit hole of upgrading FB and IronSource SDKs which just got me deeper into the reeds. Therefore, I haven't concluded why using Cocoapods 1.11.3 produced successful builds locally but not in UCB.

    I went back to basics and just kept the changes to disable bitcode and assignment of DEVELOPMENT_TEAM in custom xcproject settings and after @Benjamin-Gooding's comment, I removed the custom pre-build script and also installed Ruby 2.7.4 and Cocoapods 1.12.0 (thanks to this SO contributor) locally to mirror UCB env.

    Note that after installing these, local builds would fail due to a missing Cocoapods gems error:

    Code (JavaScript):
    1. Error running CocoaPods. Please ensure you have at least version 1.0.0.  You can install CocoaPods with the Ruby gem package manager:
    2. > sudo gem install -n /usr/local/bin cocoapods
    3. > pod setup
    4.  
    5. 'pod --version' returned status: 1
    6. output:
    7.  
    8. /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems.rb:283:in `find_spec_for_exe': can't find gem cocoapods (>= 0.a) with executable pod (Gem::GemNotFoundException)
    9.     from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems.rb:302:in `activate_bin_path'
    10.    from /Users/xxx/.gem/ruby/2.6.0/bin/pod:23:in `<main>'
    To resolve this I needed to check the 'Use Shell To Execute Cocoapod Tool' option in External Dependency Manager->iOS Resolver->Settings, which I suppose is because by default EDM is trying to access my system Ruby installation.

    Local and UCB iOS builds seem to work fine now.
     
    Last edited: Apr 19, 2023
    fassker likes this.
  35. MasahikoHagio

    MasahikoHagio

    Joined:
    Oct 15, 2021
    Posts:
    7
    Finally, check. Does that mean you could even create an archive locally?
     
  36. brockemon

    brockemon

    Joined:
    Dec 21, 2012
    Posts:
    48
    Anyone get cloud build working? I ended up trying to setup my own build system using Git Actions and GAME CI and it fails at a similar step. Not sure what fix has to be made yet, still working on it.