Bitrise Build Issue Report template
Description of the issue
I think I’ve uploaded all the files Bitrise should need to sign my iOS app. I’ve also tried using both the development and app-store deployment profiles. I’m still getting a failure to archive, even with the latest version of the step.
This could very well be an option that I have set incorrectly. I’m relatively new to both Bitrise and XCode, so user error is somewhat likely.
Environment:
Bitrise.io, Xcode 9.0.x, on macOS 10.12 (Sierra)
xcode-archive, version: 2.3.3
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 - If you have multiple different build configurations (workflows), does the issue affect all/more than one? : n/a
- If it’s an issue which happens sporadically, what’s the frequency? (e.g. Once a day ; about x% of the builds) : Every build.
- Does upgrading the build Step to the latest version help? : NO
- When did the issue start? : When I first built the deploy workflow last week.
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 ( Bitrise CLI )? If no, can it be reproduced with Docker (using the same docker images / environment we use on bitrise.io)? Related guide: Running your build locally in Docker .
I haven’t attempted to build locally with Bitrise CLI. The project does build/archive in XCode 9 locally without issue.
Other stacks
Can it be reproduced by running the build locally with our CLI ( Bitrise CLI ), 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 )?
See above.
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.
