# Can't sign iOS archive from a Flutter build step

**URL:** <https://discuss.bitrise.io/t/cant-sign-ios-archive-from-a-flutter-build-step/19848>\
**Category:** Builds\
**Tags:** code-signing, ios, flutter\
**Created:** [April 13, 2022, 3:10pm UTC](https://discuss.bitrise.io/t/cant-sign-ios-archive-from-a-flutter-build-step/19848 "2022-04-13T15:10:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![RemyDGS](https://avatars.discourse-cdn.com/v4/letter/r/ecae2f/32.png) [@RemyDGS](https://discuss.bitrise.io/u/RemyDGS)\
**Post date:** [April 13, 2022, 3:10pm UTC](https://discuss.bitrise.io/t/cant-sign-ios-archive-from-a-flutter-build-step/19848/1 "2022-04-13T15:10:00Z")

</div>

# Bitrise Build Issue Report template

## Description of the issue

_Please describe the issue here_

## Environment:

**Where did the issue happen?**

If on [Bitrise.io](http://Bitrise.io): which stack? If not on [Bitrise.io](http://Bitrise.io): on what operating system? (Plus any other information you can share)

Default (Xcode 13.3.x on macOS 12.2 (Monterey))

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

flutter-build version 0.15.1

## 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)._ : YES/NO
- _Does the issue happen sporadically, or every time?_ : All the time
- _Does upgrading the build Step to the latest version help?_ : NO
- _When did the issue start?_ : Each time I use the deploy workflow that sign the archive. The profiles and certificate are uploaded on bitrise and the step “Certificate and profile installer” is use before “Flutter build”. These steps are OK but can’t be found by xcode when trying to sign the archive.

### Local reproduction

_Can it be reproduced on your own Mac/PC by following our [local debug guide](http://discuss.bitrise.io/t/how-to-debug-your-build-locally-it-works-on-my-mac-pc-but-not-on-bitrise-io/392)? 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](http://bitrise.io) will get when it does a git clone in the clean environment! If possible please note which sections you tried._

No, it works fine on local.

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

## Build log

_Please copy paste the build’s [bitrise.io](http://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](https://www.bitrise.io/contact) ), with a link to the related Discuss issue._

> **[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:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\
**Post date:** [May 13, 2022, 3:10pm UTC](https://discuss.bitrise.io/t/cant-sign-ios-archive-from-a-flutter-build-step/19848/2 "2022-05-13T15:10:56Z")

</div>

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