# \*\* ARCHIVE FAILED \*\* CompileSwift normal arm64

**URL:** <https://discuss.bitrise.io/t/archive-failed-compileswift-normal-arm64/15970>\
**Category:** Builds\
**Created:** [March 1, 2021, 7:17am UTC](https://discuss.bitrise.io/t/archive-failed-compileswift-normal-arm64/15970 "2021-03-01T07:17:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yamini](https://avatars.discourse-cdn.com/v4/letter/y/919ad9/32.png) [@Yamini](https://discuss.bitrise.io/u/Yamini)\
**Post date:** [March 1, 2021, 7:17am UTC](https://discuss.bitrise.io/t/archive-failed-compileswift-normal-arm64/15970/1 "2021-03-01T07:17:33Z")

</div>

\*\* ARCHIVE FAILED \*\*

The following build commands failed:

CompileSwift normal arm64

CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler

(2 failures)

Not able to archive the build. Same issue even after clean build multiple times. Remove cache pull and cache push from workflows.

## Environment:

Developement

**Where did the issue happen?**

Issue happens only on Bitrise, Fastlane archive process.  
Xcode 11.5  
Mac OS 10.15.3

NOTE - Able to archive from xcode.

## 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](http://devcenter.bitrise.io/caching/about-caching/#downloading-and-deleting-caches)._ : NO
- _Does the issue happen sporadically, or every time?_ : YES, everytime
- _Does upgrading the build Step to the latest version help?_ : NO
- _When did the issue start?_ : At xcode archive step

### Local reproduction

\_Can it be reproduced on your own Mac/PC by following - NO

## Build log

> **[Log in - Bitrise](https://app.bitrise.io/users/sign_in)**
>
> Bringing back the joy of iOS & Android development through automating build, testing and support cycles.

---

<div class="post-metadata">

**Author:** ![Yamini](https://avatars.discourse-cdn.com/v4/letter/y/919ad9/32.png) [@Yamini](https://discuss.bitrise.io/u/Yamini)\
**Post date:** [March 4, 2021, 8:04am UTC](https://discuss.bitrise.io/t/archive-failed-compileswift-normal-arm64/15970/2 "2021-03-04T08:04:48Z")

</div>

It will be great if anyone can help on this please.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\
**Post date:** [April 3, 2021, 8:14am UTC](https://discuss.bitrise.io/t/archive-failed-compileswift-normal-arm64/15970/3 "2021-04-03T08:14:46Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![matthew.jones](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/matthew.jones/32/3130_2.png) [@matthew.jones](https://discuss.bitrise.io/u/matthew.jones)\
**Post date:** [April 7, 2021, 2:01pm UTC](https://discuss.bitrise.io/t/archive-failed-compileswift-normal-arm64/15970/4 "2021-04-07T14:01:10Z")

</div>

Hey Yamini!

Is this still an issue? If so, it looks like the forum automatically turned your build link into a Bitrise Sign-In link.

Could you post just the build slug? The section after /build/ in your build url.

As far as what’s happening, the actual error is probably further up in the error log than what you posted. It’s impossible to tell based only on what you were able to share.

Matthew  
Senior Customer Engineer