# Xcode 11 resolving packages fails with SSH fingerprint

**URL:** <https://discuss.bitrise.io/t/xcode-11-resolving-packages-fails-with-ssh-fingerprint/10388>\
**Category:** Builds\
**Tags:** ios\
**Created:** [September 27, 2019, 8:54pm UTC](https://discuss.bitrise.io/t/xcode-11-resolving-packages-fails-with-ssh-fingerprint/10388 "2019-09-27T20:54:41Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![johnmorrell](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/johnmorrell/32/2037_2.png) [@johnmorrell](https://discuss.bitrise.io/u/johnmorrell)\
**Post date:** [September 30, 2019, 10:37pm UTC](https://discuss.bitrise.io/t/xcode-11-resolving-packages-fails-with-ssh-fingerprint/10388/2 "2019-09-30T22:37:42Z")

</div>

I have just hit this issue and I was able to work around thanks to your reference to the Xcode issue. In my case I have a GitHub hosted iOS project with a private package hosted on a separate GitHub repo. I had to add two steps between the project checkout and building the app:

Firstly I added an ‘Activate SSH key (RSA private key)’ step, setting the ‘SSH private key in RSA format’ to a variable name, eg: ‘$DEPLOYMENT\_KEY’ (this has to be done manually in .yml). Then create a secret for that variable with the value of the private key. In my case this the private key for the GitHub Deployment Key for the private dependency.

Secondly as per the Apple workaround, I needed to add an entry to the known\_hosts file. This can be done via a ‘Script’ step. For GitHub, you can use:

```auto
for ip in $(dig @8.8.8.8 github.com +short); do ssh-keyscan github.com,$ip; ssh-keyscan $ip; done 2>/dev/null >> ~/.ssh/known_hosts

```

This is working and I expect you can achieve the same with Bitbucket.

---

_[View the full topic](https://discuss.bitrise.io/t/xcode-11-resolving-packages-fails-with-ssh-fingerprint/10388)._
