# How to commit updated AppInfo.plist after being updated by "Set Xcode Project Build Number" step **URL:** \ **Category:** Question & Answer\ **Tags:** step\ **Created:** [March 17, 2017, 8:53pm UTC](https://discuss.bitrise.io/t/how-to-commit-updated-appinfo-plist-after-being-updated-by-set-xcode-project-build-number-step/1172 "2017-03-17T20:53:42Z")\ **Posts on this page:** 1\ **Showing post:** 3
**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:** [March 18, 2017, 12:30pm UTC](https://discuss.bitrise.io/t/how-to-commit-updated-appinfo-plist-after-being-updated-by-set-xcode-project-build-number-step/1172/3 "2017-03-18T12:30:53Z")
One more note: to be able to push back into the repository: 1. You have to make sure that the SSH key (the one you can see on the **Settings** tab of the app on [bitrise.io](https://www.bitrise.io)) have **write** access to the repository. If you used the default [bitrise.io](https://www.bitrise.io) automatic SSH key registration, the key is registered as read-only, and you’ll have to delete it and add it again as a read-write key. 2. Make sure that you’re on a branch in your build. If a build is triggered by a code push / commit, you won’t be on a branch, that specific commit will be checked out. This is to prevent the build to clone another commit, e.g. if you’d push another commit to the same branch before the build could clone the commit it was started with. You can find more information about this at: [Intermittent build failures to execute push\_to\_git\_remote & how to manage build number](http://discuss.bitrise.io/t/intermittent-build-failures-to-execute-push-to-git-remote-how-to-manage-build-number/382/2) --- _[View the full topic](https://discuss.bitrise.io/t/how-to-commit-updated-appinfo-plist-after-being-updated-by-set-xcode-project-build-number-step/1172)._