ios-build-action
ios-build-action copied to clipboard
Uncaught Exception: Couldn't posix_spawn: error 7: Maybe the error shown is caused by using the wrong version of Xcode
uses: yukiarrr/[email protected]
** INTERNAL ERROR: Uncaught exception **
Uncaught Exception: Couldn't posix_spawn: error 7
Stack:
0 __exceptionPreprocess (in CoreFoundation)
1 objc_exception_throw (in libobjc.A.dylib)
2 -[NSConcreteTask launchWithDictionary:error:] (in Foundation)
3 __46-[IDEShellScriptExecutionActionOperation main]_block_invoke.212 (in IDEStandardExecutionActionsCore)
4 __DVT_CALLING_CLIENT_BLOCK__ (in DVTFoundation)
5 ___DVTAsyncPerformBlockOnMainRunLoop_block_invoke (in DVTFoundation)
6 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ (in CoreFoundation)
7 __CFRunLoopDoBlocks (in CoreFoundation)
8 __CFRunLoopRun (in CoreFoundation)
9 CFRunLoopRunSpecific (in CoreFoundation)
10 CFRunLoopRun (in CoreFoundation)
11 -[Xcode3CommandLineBuildTool _buildWithTimingSection:] (in Xcode3Core)
12 -[Xcode3CommandLineBuildTool run] (in Xcode3Core)
13 main (in xcodebuild)
14 start (in libdyld.dylib)
sh: line 1: 19175 Abort trap: 6 xcodebuild -workspace ios/MyApp.xcworkspace -scheme MyAppStaging -configuration ReleaseStaging -destination 'generic/platform=iOS' -archivePath /Users/runner/Library/Developer/Xcode/Archives/2021-12-03/output\ 2021-12-03\ 10.51.04.xcarchive clean archive
19176 Done | tee /Users/runner/Library/Logs/gym/MyApp\ Staging-MyAppStaging.log
19177 Done | xcpretty
[10:51:14]: Exit status: 134
[10:51:14]:
[10:51:14]: Maybe the error shown is caused by using the wrong version of Xcode
[10:51:14]: Found multiple versions of Xcode in '/Applications/'
[10:51:14]: Make sure you selected the right version for your project
[10:51:14]: This build process was executed using '/Applications/Xcode_12.4.app'
[10:51:14]: If you want to update your Xcode path, either
[10:51:14]:
[10:51:14]: - Specify the Xcode version in your Fastfile
[10:51:14]: ▸ xcversion(version: "8.1") # Selects Xcode 8.1.0
[10:51:14]:
[10:51:14]: - Specify an absolute path to your Xcode installation in your Fastfile
[10:51:14]: ▸ xcode_select "/Applications/Xcode8.app"
[10:51:14]:
[10:51:14]: - Manually update the path using
[10:51:14]: ▸ sudo xcode-select -s /Applications/Xcode.app
[10:51:14]:
+---------------+------------------------------+
| Build environment |
+---------------+------------------------------+
| xcode_path | /Applications/Xcode_12.4.app |
| gym_version | 2.198.1 |
| export_method | ad-hoc |
| sdk | iPhoneOS14.4.sdk |
+---------------+------------------------------+
[10:51:14]: ▸ going to read env file from root folder /Users/runner/work/myapp-***/myapp-***/ios/..
[10:51:14]: ▸ note: Using new build system
[10:51:14]: ▸ note: Building targets in parallel
[10:51:14]: ▸ ** CLEAN SUCCEEDED **
[10:51:14]:
[10:51:14]: ⬆️ Check out the few lines of raw `xcodebuild` output above for potential hints on how to solve this error
[10:51:14]: 📋 For the complete and more detailed error log, check the full log at:
[10:51:14]: 📋 /Users/runner/Library/Logs/gym/MyApp Staging-MyAppStaging.log
[10:51:14]:
[10:51:14]: Looks like fastlane ran into a build/archive error with your project
[10:51:14]: It's hard to tell what's causing the error, so we wrote some guides on how
[10:51:14]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
[10:51:14]: Before submitting an issue on GitHub, please follow the guide above and make
[10:51:14]: sure your project is set up correctly.
[10:51:14]: fastlane uses `xcodebuild` commands to generate your binary, you can see the
[10:51:14]: the full commands printed out in yellow in the above log.
[10:51:14]: Make sure to inspect the output above, as usually you'll find more error information there
[10:51:14]:
+---------------------------+-----------------------------------------------------+
| Lane Context |
+---------------------------+-----------------------------------------------------+
| DEFAULT_PLATFORM | ios |
| PLATFORM_NAME | ios |
| LANE_NAME | ios export_ipa |
| KEYCHAIN_PATH | ~/Library/Keychains/ios-build.keychain |
| ORIGINAL_DEFAULT_KEYCHAIN | "/Users/runner/Library/Keychains/login.keychain-db" |
+---------------------------+-----------------------------------------------------+
[10:51:14]: Error building the application - see the log above
+------+------------------------------+-------------+
| fastlane summary |
+------+------------------------------+-------------+
| Step | Action | Time (in s) |
+------+------------------------------+-------------+
| 1 | default_platform | 0 |
| 2 | create_keychain | 0 |
| 3 | import_certificate | 0 |
| 4 | install_provisioning_profile | 0 |
| 5 | install_provisioning_profile | 0 |
| 6 | install_provisioning_profile | 0 |
| 7 | update_code_signing_settings | 0 |
| 8 | update_project_team | 0 |
| 💥 | build_app | 23 |
+------+------------------------------+-------------+
[10:51:14]: fastlane finished with errors
[!] Error building the application - see the log above
Error: The process '/bin/bash' failed with exit code 1
How do I fix this? Please, need your help
Hey did you managed to fix it and I'm getting the same message but I haven't found a way to fix it yet...
[11:31:30]: ▸ Clean Succeeded [11:31:35]: ▸ ** ARCHIVE FAILED ** ▸ Clean Succeeded ** ARCHIVE FAILED ** [11:31:35]: Exit status: 65 [11:31:35]: [11:31:35]: Maybe the error shown is caused by using the wrong version of Xcode [11:31:35]: Found multiple versions of Xcode in '/Applications/' [11:31:35]: Make sure you selected the right version for your project [11:31:35]: This build process was executed using '/Applications/Xcode_13.1.app' [11:31:35]: If you want to update your Xcode path, either [11:31:35]: [11:31:35]: - Specify the Xcode version in your Fastfile [11:31:35]: ▸ xcversion(version: "8.1") # Selects Xcode 8.1.0 [11:31:35]: [11:31:35]: - Specify an absolute path to your Xcode installation in your Fastfile [11:31:35]: ▸ xcode_select "/Applications/Xcode8.app" [11:31:35]: [11:31:35]: - Manually update the path using [11:31:35]: ▸ sudo xcode-select -s /Applications/Xcode.app
@auliakbarh @VanniaAlfaro Hey did anyone manage to fix it, getting the same issue.