# Log Buffer overflow

**URL:** <https://discuss.bitrise.io/t/log-buffer-overflow/1570>\
**Category:** Builds\
**Tags:** fastlane, bitriseio\
**Created:** [April 26, 2017, 3:11pm UTC](https://discuss.bitrise.io/t/log-buffer-overflow/1570 "2017-04-26T15:11:42Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [April 26, 2017, 3:38pm UTC](https://discuss.bitrise.io/t/log-buffer-overflow/1570/4 "2017-04-26T15:38:00Z")

</div>

I’d suggest to switch to our Xcode Test step and add a Deploy to [Bitrise.io](http://Bitrise.io) step, as described here [Xcode exit code 65 / exit code 66 / raw-xcodebuild-output.log](http://discuss.bitrise.io/t/xcode-exit-code-65-exit-code-66-raw-xcodebuild-output-log/813)

There are other solutions, but this way you get a nicely formatted log in your Bitrise log, and if you need it you can still access the raw log (attached to the build as an artifact).

---

_[View the full topic](https://discuss.bitrise.io/t/log-buffer-overflow/1570)._