bitrise-steplib / steps-fastlane

MIT License
35 stars 19 forks source link

Fastlane does not build app that requires Swift 5.5.2 #86

Closed fearlipe closed 2 years ago

fearlipe commented 2 years ago

Troubleshooting

Useful information

Builds ok locally.

Issue description

After updating an SDK that requires Swift version 5.5.2, fastlane does not build anymore, even tho XCode build runs ok.

Bitrise info

LOG: [...] ▸ Running script 'Run Script' ▸ Running script '[CP] Embed Pods Frameworks' ▸ Running script '[CP] Copy Pods Resources' ▸ Touching Runner.app (in target 'Runner' from project 'Runner') ARCHIVE FAILED The following build commands failed: Run custom shell script 'Run Script' (1 failure) [09:35:50]: Exit status: 65 [09:35:50]: [09:35:50]: Maybe the error shown is caused by using the wrong version of Xcode [09:35:50]: Found multiple versions of Xcode in '/Applications/' [09:35:50]: Make sure you selected the right version for your project [09:35:50]: This build process was executed using '/Applications/Xcode-13.2.1.app' [09:35:50]: If you want to update your Xcode path, either [09:35:50]: [09:35:50]: - Specify the Xcode version in your Fastfile [09:35:50]: ▸ xcversion(version: "8.1") # Selects Xcode 8.1.0 [09:35:50]: [09:35:50]: - Specify an absolute path to your Xcode installation in your Fastfile [09:35:50]: ▸ xcode_select "/Applications/Xcode8.app" [09:35:50]: [09:35:50]: - Manually update the path using [09:35:50]: ▸ sudo xcode-select -s /Applications/Xcode.app [09:35:50]: +-------------+--------------------------------+ Build environment +-------------+--------------------------------+ xcode_path /Applications/Xcode-13.2.1.app gym_version 2.199.0 sdk iPhoneOS15.2.sdk +-------------+--------------------------------+ [09:35:50]: ▸ builtin-validationUtility /Users/vagrant/Library/Developer/Xcode/DerivedData/Runner-fvdlvfvunbwmbcgkbjykdeexifra/Build/Intermediates.noindex/ArchiveIntermediates/Runner/InstallationBuildProductsLocation/Applications/Runner.app [09:35:50]: ▸ Touch /Users/vagrant/Library/Developer/Xcode/DerivedData/Runner-fvdlvfvunbwmbcgkbjykdeexifra/Build/Intermediates.noindex/ArchiveIntermediates/Runner/InstallationBuildProductsLocation/Applications/Runner.app (in target 'Runner' from project 'Runner') [09:35:50]: ▸ cd /Users/vagrant/git/ios [09:35:50]: ▸ /usr/bin/touch -c /Users/vagrant/Library/Developer/Xcode/DerivedData/Runner-fvdlvfvunbwmbcgkbjykdeexifra/Build/Intermediates.noindex/ArchiveIntermediates/Runner/InstallationBuildProductsLocation/Applications/Runner.app [09:35:50]: [09:35:50]: ⬆️ Check out the few lines of raw xcodebuild output above for potential hints on how to solve this error [09:35:50]: 📋 For the complete and more detailed error log, check the full log at: [09:35:50]: 📋 /var/folders/62/0p2cg52j6r16xjxfqch4vgt40000gn/T/fastlane_logs133349486/gym/Runner-Runner.log [09:35:50]: [09:35:50]: Looks like fastlane ran into a build/archive error with your project [09:35:50]: It's hard to tell what's causing the error, so we wrote some guides on how [09:35:50]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/ [09:35:50]: Before submitting an issue on GitHub, please follow the guide above and make [09:35:50]: sure your project is set up correctly. [09:35:50]: fastlane uses xcodebuild commands to generate your binary, you can see the [09:35:50]: the full commands printed out in yellow in the above log. [09:35:50]: Make sure to inspect the output above, as usually you'll find more error information there [09:35:50]: +------------------+----------+ Lane Context +------------------+----------+ DEFAULT_PLATFORM ios PLATFORM_NAME ios LANE_NAME ios beta BUILD_NUMBER 916 +------------------+----------+ [09:35:50]: Error building the application - see the log above +------+------------------------+-------------+ fastlane summary +------+------------------------+-------------+ Step Action Time (in s) +------+------------------------+-------------+ 1 default_platform 0 2 xcversion 0 3 xcode_select 0 4 increment_build_number 3 💥 build_app 417 +------+------------------------+-------------+ [09:35:50]: fastlane finished with errors [!] Error building the application - see the log above Fastlane command: (fastlane "beta") failed If you want to send an issue report to fastlane (https://github.com/fastlane/fastlane/issues/new), you can find the output of fastlane env in the following log file: /Users/vagrant/deploy/fastlane_env.log $ fastlane "env" swift-driver version: 1.26.21 Command failed, error: exit status 1

+---+---------------------------------------------------------------+----------+ | x | fastlane@3 (exit code: 1) | 7.7 min | +---+---------------------------------------------------------------+----------+ | Issue tracker: https://github.com/bitrise-io/steps-fastlane/issues | | Source: https://github.com/bitrise-io/steps-fastlane | +---+---------------------------------------------------------------+----------+

ofalvai commented 2 years ago

Hey @fearlipe 👋

The latest stable Bitrise stack (Xcode 13.2) contains Swift 5.5.1: https://github.com/bitrise-io/bitrise.io/blob/gen2-system-reports-w52/system_reports/osx-xcode-13.2.x.log#L1109

May I ask what is your local setup that builds your project successfully?

bitrise-coresteps-bot commented 2 years ago

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

bitrise-coresteps-bot commented 2 years ago

I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.