Learn what Felgo offers to help your business succeed. Start your free evaluation today! Felgo for Your Business

Forums

OverviewFelgo 3 Support (Qt 5) › [Cloud Builds] iOS app fails to install

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #25053

    Ian

    I’m seeing the following error when trying to build my iOS app:

     

    [03:37:41 +0000]: $ set -o pipefail ﹠﹠ xcodebuild -scheme iosproject -project ./iosproject.xcodeproj -destination ‘generic/platform=iOS’ -archivePath ~/Library/Developer/Xcode/Archives/2023-05-28/iosproject\ 2023-05-28\ 03.37.41.xcarchive archive | tee ~/Library/Logs/gym/iosproject-iosproject.log | xcpretty –no-color
    [03:37:46 +0000]: Run script build phase ‘Qt Qmake’ 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 ‘Qt Preprocess’ from project ‘iosproject’)
    [03:37:46 +0000]: Run script build phase ‘Qt Preprocessors’ 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 ‘Qt Preprocess’ from project ‘iosproject’)
    [03:37:46 +0000]: Traditional headermap style is no longer supported; please migrate to using separate headermaps and set ‘ALWAYS_SEARCH_USER_PATHS’ to NO. (in target ‘iosproject’ from project ‘iosproject’)
    [03:37:46 +0000]: Run script build phase ‘Qt Postlink’ 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 ‘iosproject’ from project ‘iosproject’)
    [03:37:46 +0000]: ** ARCHIVE FAILED **
    Run script build phase ‘Qt Qmake’ 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 ‘Qt Preprocess’ from project ‘iosproject’)
    Run script build phase ‘Qt Preprocessors’ 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 ‘Qt Preprocess’ from project ‘iosproject’)
    Traditional headermap style is no longer supported; please migrate to using separate headermaps and set ‘ALWAYS_SEARCH_USER_PATHS’ to NO. (in target ‘iosproject’ from project ‘iosproject’)
    Run script build phase ‘Qt Postlink’ 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 ‘iosproject’ from project ‘iosproject’)
    ** ARCHIVE FAILED **
    [03:37:46 +0000]: Exit status: 65
    [03:37:46 +0000]:
    [03:37:46 +0000]: Maybe the error shown is caused by using the wrong version of Xcode
    [03:37:46 +0000]: Found multiple versions of Xcode in ‘/Applications/’
    [03:37:46 +0000]: Make sure you selected the right version for your project
    [03:37:46 +0000]: This build process was executed using ‘/Applications/Xcode-14.1.app’
    [03:37:46 +0000]: If you want to update your Xcode path, either
    [03:37:46 +0000]:
    [03:37:46 +0000]: – Specify the Xcode version in your Fastfile
    [03:37:46 +0000]: xcversion(version: “8.1”) # Selects Xcode 8.1.0
    [03:37:46 +0000]:
    [03:37:46 +0000]: – Specify an absolute path to your Xcode installation in your Fastfile
    [03:37:46 +0000]: xcode_select “/Applications/Xcode8.app”
    [03:37:46 +0000]:
    [03:37:46 +0000]: – Manually update the path using
    [03:37:46 +0000]: sudo xcode-select -s /Applications/Xcode.app
    [03:37:46 +0000]:
    +—————+——————————+
    | Build environment |
    +—————+——————————+
    | xcode_path | /Applications/Xcode-14.1.app |
    | gym_version | 2.213.0 |
    | export_method | development |
    | sdk | iPhoneOS16.1.sdk |
    +—————+——————————+
    [03:37:46 +0000]: warning: Run script build phase ‘Qt Preprocessors’ 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 ‘Qt Preprocess’ from project ‘iosproject’)
    [03:37:46 +0000]: ~/project/repo/build-ios/iosproject.xcodeproj: warning: Building with bitcode is deprecated. Please update your project and/or target settings to disable bitcode. (in target ‘iosproject’ from project ‘iosproject’)
    [03:37:46 +0000]: ~/project/repo/build-ios/iosproject.xcodeproj: error: No signing certificate “iOS Development” found: No “iOS Development” signing certificate matching team ID “94SKXWG4KH” with a private key was found. (in target ‘iosproject’ from project ‘iosproject’)
    [03:37:46 +0000]: warning: Traditional headermap style is no longer supported; please migrate to using separate headermaps and set ‘ALWAYS_SEARCH_USER_PATHS’ to NO. (in target ‘iosproject’ from project ‘iosproject’)
    [03:37:46 +0000]: warning: Run script build phase ‘Qt Postlink’ 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 ‘iosproject’ from project ‘iosproject’)
    [03:37:46 +0000]:
    [03:37:46 +0000]: Check out the few lines of raw xcodebuild output above for potential hints on how to solve this error
    [03:37:46 +0000]: For the complete and more detailed error log, check the full log at:
    [03:37:46 +0000]: ~/Library/Logs/gym/iosproject-iosproject.log
    [03:37:46 +0000]:
    [03:37:46 +0000]: Your export_method in gym is defined as development
    [03:37:46 +0000]: which might cause problems when signing your application
    [03:37:46 +0000]: Are you sure want to build and export for development?
    [03:37:46 +0000]: Please make sure to define the correct export methods when calling
    [03:37:46 +0000]: gym in your Fastfile or from the command line
    [03:37:46 +0000]:
    [03:37:46 +0000]:
    [03:37:46 +0000]: Looks like fastlane ran into a build/archive error with your project
    [03:37:46 +0000]: It’s hard to tell what’s causing the error, so we wrote some guides on how
    [03:37:46 +0000]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
    [03:37:46 +0000]: Before submitting an issue on GitHub, please follow the guide above and make
    [03:37:46 +0000]: sure your project is set up correctly.
    [03:37:46 +0000]: fastlane uses xcodebuild commands to generate your binary, you can see the
    [03:37:46 +0000]: the full commands printed out in yellow in the above log.
    [03:37:46 +0000]: Make sure to inspect the output above, as usually you’ll find more error information there
    [03:37:46 +0000]:
    +——————+————-+
    | Lane Context |
    +——————+————-+
    | DEFAULT_PLATFORM | ios |
    | PLATFORM_NAME | ios |
    | LANE_NAME | ios release |
    +——————+————-+
    [03:37:46 +0000]: Error building the application – see the log above
    +——+—————————–+————-+
    | fastlane summary |
    +——+—————————–+————-+
    | Step | Action | Time (in s) |
    +——+—————————–+————-+
    | 1 | default_platform | 0 |
    | 2 | update_project_team | 0 |
    | 3 | update_project_provisioning | 0 |
    | | build_ios_app | 38 |
    +——+—————————–+————-+
    [03:37:46 +0000]: fastlane finished with errors
    [!] Error building the application – see the log above
    – Unsuccessful build

    #25054

    Ian

    Nevermind, I figured this out.

     

    My certificate / key bundle (p12 file) did not have the distribution cert pair, just the dev signing certificate.  uploading the right cert fixed this.

Viewing 2 posts - 1 through 2 (of 2 total)

RSS feed for this thread

You must be logged in to reply to this topic.

Qt_Technology_Partner_RGB_475 Qt_Service_Partner_RGB_475_padded