# Bitrise adding additional directory in build path? **URL:** \ **Category:** Question & Answer\ **Created:** [February 13, 2017, 11:46pm UTC](https://discuss.bitrise.io/t/bitrise-adding-additional-directory-in-build-path/770 "2017-02-13T23:46:28Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [February 14, 2017, 10:07am UTC](https://discuss.bitrise.io/t/bitrise-adding-additional-directory-in-build-path/770/2 "2017-02-14T10:07:28Z")
How do you run this xcode command? With an Xcode step or from a **Script** step? In general there’s absolutely no Bitrise specific thing going on. Even if you use an Xcode step that prints the whole `xcodebuild` command it will run, and it does not modify anything on that command, it just runs it. I’d suggest you to try these local debug/reproduction steps, and let us know if that helps / how that goes: > [@How to debug your build locally / "It works on my Mac/PC but not on bitrise.io"](http://discuss.bitrise.io/t/how-to-debug-your-build-locally-it-works-on-my-mac-pc-but-not-on-bitrise-io/392): > > If the build works on your local Mac/PC but not on [bitrise.io](https://www.bitrise.io), that’s usually because of uncommitted / gitignored files or a tool version difference. There can be other reasons, for example in case of iOS code signing errors it’s usually because a code signing file which is available on your Mac, but you did not upload it to [bitrise.io](https://www.bitrise.io) and so it’s not available there. In any case, the first steps you should try, preferably before you’d report the issue (as this will be the first thing we’ll ask… > [@samjarman](#): > > My current work-around is to look for the user “vagrant” in my build script Is this build script an Xcode Build Phase script, or you’re referring to a build step/script? --- _[View the full topic](https://discuss.bitrise.io/t/bitrise-adding-additional-directory-in-build-path/770)._