[BUG]: /usr/bin/xcodebuild failed with return code: 65 #19405
Comments
github-actions
bot
added
Area: Release
triage
Area: ABTT
|
Hi @iCodeWoods, Could you please, provide more details about your inputs and signing configuration? |
|
Hi @kirill-ivlev , I believe it's not a problem with signing because it fails quickly even before starting the compilation. We have four build machines: one is normal (indicating the project itself is fine), while the other three machines fail before the compilation starts. I don't have a minimal project. This issue has persisted for a long time. Since we have one successful machine, it doesn't block our release. However, there are occasions when we need to wait if we want to have two or more builds simultaneously. |
|
@iCodeWoods, on that machine, where you build failing from the Azure agent, are you able to build it from the terminal? |
|
@kirill-ivlev Yes, success can be achieved by using the same command that was copied from the agent to the local terminal. |
|
I'm having a similar issue. Fails quite quickly. If you're using command line directly, it does build but with I've only started noticing this since adopting Swift macros. In order to use swift macros. I have followed the steps to enable macro usage. You can either pass in a compiler flag |
|
I am also seeing this: The error occurs at the very start of compilation, however it possibly is a signing issue because if we turn signing off the compile continues. |
@Muhammed9991 Thanks, but we didn't use SwiftMacro. |
@eoinnorris This sounds strange; didn't signing happen in the very last stage? |
yes is is strange. |
We're also seeing the same issue, adding to @eoinnorris that not only the commit it's exactly the same (including the app and yaml pipeline code), but also the agent OS and image versions are exactly the same Till the 12th of January worked and now starting from the 19th of January is throwing Also if it can help, yes the error appears at the "start of compilation", but still after 4/5 minutes the task started to run P.s. |
Apologies for the confusion, after extensive debugging, we figure the issue out, devs pointed some swift packages to main branch instead of using a release version, all works good now, thanks! |
Hi @eoinnorris , Are you still facing this issue, or have you resolved it? I tried using a new .p12, but it still fails at the beginning of the build. |
In your case, there does seem to be an error, but it's only displaying '/usr/bin/xcodebuild' failed with exit code 65 without providing specific error information. Is there a way we can enhance the details of this error? @kirill-ivlev |
add args: '-verbose' to get more output. In our case some of our SPM libraries had updated to change their Xcode project files, both the reachability and realm project did something, it looks like they added a security markdown at the least. What we found was that the build failed on the pipeline but not on our local builds which mimic the pipeline build exactly. Without knowing the full underlying cause it looks like code signing failed because of additional assets in the framework -- the security file I assume. You get this with the verbose log. It looks like this works with Xcode 15.x on macOS 14.x but not for Xcode running on pre Sonoma. The pipeline uses Ventura as the latest OS, presumably they do this until Ventura is not supported anymore, at which time it will magically fix itself. In the meantime look at recent updates in your SPM list ( or Cocoa pods or whatever you use) |
|
Fixed. We did have some SwiftUI previews in one of our kit and that can apparently cause issues if Swift 5.9 is not installed on the build machines. |
Can you help me to install Swift 5.9 on build machines? Thanks in advance. |
I am still having the same issue... I am not very familiar with apple/xcode development, my project uses Ionic/capacitor.. please help! (certificates are all valid, I checked that) This is my release pipeline: |
|
hi @Valentin-Pommee-Macaw did you find a resolution by any chance ? I have also been setting up a pipeline for an Ionic build and am stuck banging my head on this same 65 error code... |
|
Hey @FauxObsolete, |
|
thanks for the reply @Valentin-Pommee-Macaw. |
|
Anyone having also this problem. We had a script that modified the capacitor project project for multiple tenants, but we forgot to replace the applicationIdentifier in the |
|
@otiv33 It's not my case, he's correct. Could a wrong configuration regarding the use of flavors cause this? (I refer to the configuration in the pipeline) |
|
2024-12-13T09:58:37.5391350Z Run script build phase '[CP] Embed Pods Frameworks' 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 'App' from project 'App') I get this error, How to find out the cause?? |
|
Anyone? |
New issue checklist
Task name
Xcode
Task version
5.231.5
Issue Description
/usr/bin/xcodebuild failed with return code: 65before build.But locally build is successful.
But locally build is successful.
But locally build is successful.
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Mac mini Apple M2 14.1.2 (23B92)
Relevant log output
Full task logs with system.debug enabled
No response
Repro steps
No response
The text was updated successfully, but these errors were encountered: