Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Question ios cloud build failed.

Discussion in 'Unity Build Automation' started by charmingny, Apr 23, 2022.

  1. charmingny

    charmingny

    Joined:
    Nov 1, 2021
    Posts:
    5
    Android cloud build was still okay till now. IOS cloud build failed. I was able to build both ios and android successfully 7 days ago. And I added unity meditation package and I revoked old ios certificates and created new and updated the build config. now I am stuck with this error. I tried various things to solve. I need helps please. I am not familiar with these things.

    /usr/bin/touch -c /BUILD_PATH/Library/Developer/Xcode/DerivedData/Unity-iPhone-amftlspngpdiwddaebeetbobruep/Build/Intermediates.noindex/ArchiveIntermediates/Unity-iPhone/InstallationBuildProductsLocation/APPLICATION_PATH/The\ XXX\ Game.app
    8069: ▸ /BUILD_PATH/mm-gz.xxx.ios_adhoc/temp20220423-5110-1dcx8bl/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 15.2.99. (in target 'Protobuf' from project 'Pods')
    8070: ▸ ** ARCHIVE SUCCEEDED **
    8071: ⬆️ Check out the few lines of raw `xcodebuild` output above for potential hints on how to solve this error
    8072: For the complete and more detailed error log, check the full log at:
    8073: /BUILD_PATH/Library/Logs/gym/The XXX Game-Unity-iPhone.log
    8074: Looks like fastlane ran into a build/archive error with your project
    8075: It's hard to tell what's causing the error, so we wrote some guides on how
    8076: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
    8077: Before submitting an issue on GitHub, please follow the guide above and make
    8078: sure your project is set up correctly.
    8079: fastlane uses `xcodebuild` commands to generate your binary, you can see the
    8080: the full commands printed out in yellow in the above log.
    8081: Make sure to inspect the output above, as usually you'll find more error information there
    8082: +------------------+-----------+
    8083: | Lane Context |
    8084: +------------------+-----------+
    8085: | DEFAULT_PLATFORM | ios |
    8086: | PLATFORM_NAME | ios |
    8087: | LANE_NAME | ios build |
    8088: +------------------+-----------+
    8089: Error packaging up the application
    8090: +------+---------------------------------------------------------------+-------------+
    8091: | fastlane summary |
    8092: +------+---------------------------------------------------------------+-------------+
    8093: | Step | Action | Time (in s) |
    8094: +------+---------------------------------------------------------------+-------------+
    8095: | 1 | Verifying fastlane version | 0 |
    8096: | 2 | default_platform | 0 |
    8097: | 3 | set_info_plist_value | 0 |
    8098: | 4 | update_project_provisioning | 0 |
    8099: | 5 | sed -i '' '/PROVISIONING_PROFILE_SPECIFIER/d;/DEVELOPMENT_TEA | 0 |
    8100: | | gym | 438 |
    8101: +------+---------------------------------------------------------------+-------------+
    8102: fastlane finished with errors
    8103: [!] Error packaging up the application
    8104: ! build of 'ios_adhoc' failed. ! xcode build failed.
     
  2. charmingny

    charmingny

    Joined:
    Nov 1, 2021
    Posts:
    5
    I removed all ad related packages back. Still same error. so, it is because of certificates. I will try to generate again.
     
  3. rbitard

    rbitard

    Joined:
    Jan 11, 2022
    Posts:
    189
    I have the same problem did you find a solution ?
     
  4. Mishganches

    Mishganches

    Joined:
    Mar 23, 2014
    Posts:
    31
  5. rbitard

    rbitard

    Joined:
    Jan 11, 2022
    Posts:
    189
    @Mishganches for now I payed for nothing, I hope it'll work one day
     
  6. Benjamin-Gooding

    Benjamin-Gooding

    Unity Technologies

    Joined:
    Apr 12, 2022
    Posts:
    242
    Try setting the Ruby version in advanced settings to Ruby 2.7.4. That is using a newer version of Fastlane than what is being used with Ruby 2.4.2