For Swift 4.2, Bitrise can't build, but my mac can build


#1

Bitrise Build Issue Report template

Description of the issue

After updating to Swift 4.2, Bitrise can’t build, but my mac can build

Environment:

Where did the issue happen?

Xcode 10.0.x, on Mac OS 10.13 (High Sierra)

Which build Step causes the issue and which version of the step?

xcode-archive always latest

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:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : NO
  • Does the issue happen sporadically, or every time? :every time
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? :

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 ( https://www.bitrise.io/cli )? If no, can it be reproduced with Docker (using the same docker images / environment we use on bitrise.io)? Related guide: http://devcenter.bitrise.io/docker/run-your-build-locally-in-docker/ .

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 - https://www.bitrise.io/contact ), with a link to the related Discuss issue.


#2

Hi @studygear,

Sorry to hear about the issue. Can you please include a build URL where we could look into it?


#3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.