Bitrise Build Issue Report template
Description of the issue
xcodebuild commands ends with this message
The following build commands failed:
CompileSwift normal arm64 /Users/vagrant/git/**/*.swift
CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler
Environment:
Where did the issue happen?
If on Bitrise.io: which stack? If not on Bitrise.io: on what operating system? (Plus any other information you can share)
Which build Step causes the issue and which version of the step?
xcode-archive 3.2.0
Reproducibility
- Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
-
Does a rebuild without caches help? (You can remove the
Cache:PullandCache:Pushsteps temporarily to not to use the cache, or you can delete all the caches on theSettingstab of the app. : NO - Does the issue happen sporadically, or every time? : sporadically
- Does upgrading the build Step to the latest version help? : NO
- When did the issue start? : today(2021/05/11), but I faced the same problem last month. At the previous time the same issue happened, it is fixed without any change after a few days.
Local reproduction
Can it be reproduced on your own Mac/PC by following our local debug guide? Please follow at least the first section (“Testing with a full clean git clone”) to make sure to test the state of the code what bitrise.io will get when it does a git clone in the clean environment! If possible please note which sections you tried.
Local reproduction: Linux / Android (docker based) stack builds
Can it be reproduced by running the build locally, after doing a new git clone of the repository into the /tmp directory and running the build from there with the Bitrise CLI ( Bitrise CLI )? If no, can it be reproduced with Docker (using the same docker images / environment we use on bitrise.io)? Related guide: Redirecting… .
Build log
Please copy paste the build’s bitrise.io URL here (or if the issue happens somewhere else then the full logs), or if you can’t share the url / log here then send the url or full log through a private channel (e.g. email - Contact us ), with a link to the related Discuss issue.
