# Keychain logging from firebase

**URL:** <https://discuss.bitrise.io/t/keychain-logging-from-firebase/13296>\
**Category:** Builds\
**Created:** [June 10, 2020, 9:57pm UTC](https://discuss.bitrise.io/t/keychain-logging-from-firebase/13296 "2020-06-10T21:57:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![RyanCrandall](https://avatars.discourse-cdn.com/v4/letter/r/8e8cbc/32.png) [@RyanCrandall](https://discuss.bitrise.io/u/RyanCrandall)\
**Post date:** [June 10, 2020, 9:57pm UTC](https://discuss.bitrise.io/t/keychain-logging-from-firebase/13296/1 "2020-06-10T21:57:51Z")

</div>

![02](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/3/3301783742e411a05db7ac708b7a742164eae99a.png)  
I have built a workflow to run which builds for the simulator then runs pytest. Pytest actually runs well, and the steps to send\_keys to the username/password fields work, but I am unable to login because of some key chain error.

In my certification step, it runs without error and the same as my other workflows. However, I cannot log in for the error shown in the photo. We use firebase to log in, and am wondering if that is not playing nice to bitrise builds. If I build out of bitrise, it works fine.

```auto
Configs:
 - CertificateURL: https://con***5e3
 - CertificatePassphrase: 
 - ProvisioningProfileURL: https://con***9d6
 - InstallDefaults: yes
 - DefaultCertificateURL: https://s3-***p12
 - DefaultCertificatePassphrase: ***
 - DefaultProvisioningProfileURL: https://s3-***ion
 - KeychainPath: /Users/[REDACTED]/Library/Keychains/login.keychain
 - KeychainPassword: ***
Default Certificate given
Provided Certificate count: 2
Default Provisioning Profile given
Provided Provisioning Profile count: 3
Keychain (/Users/[REDACTED]/Library/Keychains/login.keychain) does not exist
 Checking (/Users/[REDACTED]/Library/Keychains/login.keychain-db)
Downloading & installing Certificate(s)
Downloading certificate: 1/2
Downloading certificate: 2/2
| |
+---+---------------------------------------------------------------+----------+
| ✓ | certificate-and-profile-installer | 7.59 sec |
+---+---------------------------------------------------------------+----------+`
```

---

<div class="post-metadata">

**Author:** ![bitce](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/bitce/32/1639_2.png) [@bitce](https://discuss.bitrise.io/u/bitce)\
**Post date:** [June 25, 2020, 9:21am UTC](https://discuss.bitrise.io/t/keychain-logging-from-firebase/13296/2 "2020-06-25T09:21:15Z")

</div>

Hi @RyanCrandall! Sorry to hear about the issue. Can you please include a build URL to a relevant build where the issue is happening?

---

<div class="post-metadata">

**Author:** ![RyanCrandall](https://avatars.discourse-cdn.com/v4/letter/r/8e8cbc/32.png) [@RyanCrandall](https://discuss.bitrise.io/u/RyanCrandall)\
**Post date:** [July 7, 2020, 8:48pm UTC](https://discuss.bitrise.io/t/keychain-logging-from-firebase/13296/3 "2020-07-07T20:48:03Z")

</div>

I finally fixed the issue here, but it turns out that in the BUILD FOR IOS SIMULATOR step has CODE\_SIGNING set to false by default and in the UI there is no way to change this, so I never noticed.

Please I’d recommend changing this to prevent further issues like this happening. Essentially my code has to add CODE\_SIGNING=TRUE as an extra option afterwards, but I should have the option to change it.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\
**Post date:** [August 6, 2020, 8:48pm UTC](https://discuss.bitrise.io/t/keychain-logging-from-firebase/13296/4 "2020-08-06T20:48:04Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.