gym error on macOS Ventura 13.0, Xcode 14.0.1 & Xcode 14.1 #20810
Comments
|
@Daemonson as written in the logs - seems that you have multiple versions of Xcode on your machine and for fastlane it's not clear which one should be used. Can this be the case? |
|
@fbaumgart I only have one Xcode on my mac. This is not the case. As I described above, it works before I upgrade my mac os to Ventura 13.0. And my colleagues also encounter the same case. |
|
Having same issue here after upgrade fastlane to And my fastlane is: I'm pretty sure match download |
|
It seems like some message mentioned on issue apple/swift#20784 is useful for you. |
I suppose something went wrong when it executed the code sign action. Maybe permission error on macOS 13.0 or something else. |
|
@Daemonson Tks, I will dig in this problem by the issue you mention, but it still have problem when use xcode: 14.x on CircleCI, I could only local build development recently. |
|
After some info mention above, I try to add match |
Thanks for your information. I found that it works when I build with |
|
Maybe something changed about the toolchain by the system on Ventura 13.0. I build success for all |
|
This issue might be the reason why it fails. apple/swift-driver#1271 |
|
Finally, I've resolved this error by changing some SDKs from Those SDKs showed error info with If the SDK you linked in your project doesn't offer |
|
@Daemonson I'm using Flutter right now so I'm not sure the solution of flutter environment. So I need to have additional job setting before |
Sorry, I don't use Flutter in my project. I'm not sure if it's the This is the case that I encountered. And I can fix it with the solution I mentioned above. |
Daemonson
changed the title
|
I was also facing the same |
|
any update? same issue |
|
+1 monterey 12.6.1 keep fail too on Bitrise "Xcode 14.1.x, on macOS Monterey 12.5" stack |
|
anyone can help? my company is waiting my build at least 1 week. Thank you so much. |
|
I was getting the archive failed exit code 65 with no helpful logging after updating to xcode 14 on CI. It was a code signing issue. I needed to change my Fastfile's gym command to include the |
|
Hello, could you please expand what should I do? Currently I have script in ruby It is working allright for Xcode 13.4 on bitrise. But same build is crashing (Exit status: 65) when I try increase stack to any version of Xcode 14. |
|
@SwiftyMike are you using any swift packages that include bundled resources? There is an issue noted issue with the Xcode command line utilities attempting to sign resource bundles when it shouldn't: https://forums.swift.org/t/xcode-14-beta-code-signing-issues-when-spm-targets-include-resources/59685 Several other related issues: |
|
i confirm, this solution worked for me. You need to add some xcargs to the Gym command (either in your Gymfile, or in the gym() command in your lane). |
|
Unfortunately didn't work for me :( |
|
Hi, Not working too with Xcode 14.2, any update? Thanks |
|
Hi, |
|
This seemed to solve the problem for our app by adding this to the Podfile. Hope this helps someone with the pending apple requirement starting in April to build on xcode 14 post_install do |installer|
installer.generated_projects.each do |project|
project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings["DEVELOPMENT_TEAM"] = "XXXXX"
# This is necessary for Xcode 14, because it signs resource bundles by default
# when building for devices
config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
end
end
end
react_native_post_install(installer)
__apply_Xcode_12_5_M1_post_install_workaround(installer)
end |
|
I <3 U @tjbenton |
|
Not working on Xcode 14.3. Facing same issue. |
|
on another project I also had to add these to the Podfile. Or you can go into xcode and change it in the build settings. This allowed me to get it to run on the simulator. Seems to be related to the the new Apple M2 Chip because it wasn't needed for other team members with older machines config.build_settings['ONLY_ACTIVE_ARCH'] = 'YES'
config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
|
|
I have the same issue, I cannot build ipa via gym |
|
This one might help |
|
I cannot build ipa via gym but able to build via XCODE |
|
Hi, My last error trace Thank you very much |
Same here! Any update....
|
|
I have read in several threads about the same issue, corresponding with rsync (since the copy can't find the files I guess) because I am running into the same issue. Therefore I can confirm that Xcode 14.3.1 does not work with fastlane |
This worked out fine for me. Adding the -f to the framework pods did the trick! Thank you very much for sharing. |
|
Hi @IJustDev, Thanks for the trick but sadly it is not an option for me because my relative My CI recreated it at each job, basing on |
|
Hi, Always the same error with Xcode 15.1.0 beta 3 on CircleCI... |
|
I have the same issue trying Unity Build Automation for an ios deploy. Is this in general just what happens when fastlane updates and xcode isn't keeping up? |
and others
New Issue Checklist
Issue Description
Command executed
Complete output when running fastlane, including the stack trace and command used
Environment
I encounter this problem after I upgrade my mac os to Ventura 13.0. But It works with Xcode14.0.1 on macOS 12.6.1.
It works for about a few minutes on my project till it fails. I can't find any useful error message that told me where is the error. It seems that gym fails before the 'code sign' action I suppose.
The text was updated successfully, but these errors were encountered: