Xamarin iOS TestCloud step failes with "code object is not signed at all" error

Question & Answer Builds
1

Bitrise Build Issue Report template

Description of the issue

Since late December I’ve been getting a problem on the xamarin-test-cloud-for-ios step. The build of my iOS app fails for the following reason: “code object is not signed at all In architecture: armv7”.

Having googled this, it seems related to a recent bug in Xamarin itself:

Environment:

Bitrise: Xamarin Alpha with Xcode 8.2, on macOS 10.12 (Sierra)
xamarin-test-cloud-for-ios (latest version)

Reproducibility

  • _Does a “Rebuild” help?
    NO

  • _Does a rebuild without caches help?
    Not using caches

  • _If you have multiple different build configurations (workflows), does the issue affect all/more than one?
    Only using one workflow

  • If it’s an issue which happens sporadically, what’s the frequency? (e.g. Once a day ; about x% of the builds) :
    100%

  • Does upgrading the build Step to the latest version help? :
    NO

  • When did the issue start? :
    Late December

Linux/Android 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: https://bitrise-io.github.io/devcenter/docker/run-your-build-locally-in-docker/ .

Other stacks

Can it be reproduced by running the build locally with our CLI ( https://www.bitrise.io/cli ), 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 )?

Build log

Please attach the build log (you can download the build log from the build’s page, once the build is finished, using the “Download log” button - floating at the bottom right corner of the log viewer), or if you can’t attach the whole log then send the full log through a private channel (e.g. email - Contact us ), with a link to the related GitHub issue.

2

Did you try it on the Xamarin Beta / Stable channels? If it’s a recent issue, maybe those are not affected.

3

@freever Did you try it on the Xamarin Beta / Stable channels?

4

Yes, it works on the stable channels. I also got a reply from Xamarin saying that the bug fix is working its way through the system and should be fixed on alpha soon.

5

Awesome to hear, thanks for reporting!

P.S.there was a new Xamarin Beta version released recently (http://releases.xamarin.com/) - this weekend’s Xamarin stack updates will include that on the Xamarin Beta stack, hopefully that includes the fix for the Beta channel now :wink: