# Firebase dSYM Upload step doesn't work

**URL:** <https://discuss.bitrise.io/t/firebase-dsym-upload-step-doesnt-work/11698>\
**Category:** Tooling Issues\
**Tags:** fabric, firebase\
**Created:** [January 23, 2020, 8:35am UTC](https://discuss.bitrise.io/t/firebase-dsym-upload-step-doesnt-work/11698 "2020-01-23T08:35:32Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![vladimirbakalov](https://avatars.discourse-cdn.com/v4/letter/v/ecb155/32.png) [@vladimirbakalov](https://discuss.bitrise.io/u/vladimirbakalov)\
**Post date:** [January 23, 2020, 8:35am UTC](https://discuss.bitrise.io/t/firebase-dsym-upload-step-doesnt-work/11698/1 "2020-01-23T08:35:32Z")

</div>

The **Firebase dSYM Upload** step won’t work if the app was previously linked from Fabric to Firebase Crashlytics. The dSYM files are still missing in Fabric after successful BitRise builds. No issues are reported by the step when building.

In the new Firebase dSYM uploading instructions it says:

> **Important:** If you’re working with an app that you previously linked from Fabric to Firebase Crashlytics, pass in your Fabric API Key to run the `upload symbols` script. That is, in the following options to run the script, use `-a fabric-api-key` instead of `-gsp path/to/GoogleService-Info.plist` .

[https://firebase.google.com/docs/crashlytics/get-deobfuscated-reports?platform=ios&authuser=1](https://firebase.google.com/docs/crashlytics/get-deobfuscated-reports?platform=ios&authuser=1)

But there is no way the Fabric API key could be added to the workflow step.

---

<div class="post-metadata">

**Author:** ![non-binary](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/non-binary/32/2764_2.png) [@non-binary](https://discuss.bitrise.io/u/non-binary)\
**Post date:** [February 3, 2020, 7:16pm UTC](https://discuss.bitrise.io/t/firebase-dsym-upload-step-doesnt-work/11698/2 "2020-02-03T19:16:24Z")

</div>

Hi @moodagent,

Thank you for sending this over.

I have reached out to the tooling team about this and will follow-up as soon as I hear back from them.

Please don’t hesitate to follow-up if you have any questions or updates in the meantime.

Thanks,  
Luna

---

<div class="post-metadata">

**Author:** ![non-binary](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/non-binary/32/2764_2.png) [@non-binary](https://discuss.bitrise.io/u/non-binary)\
**Post date:** [February 4, 2020, 12:42pm UTC](https://discuss.bitrise.io/t/firebase-dsym-upload-step-doesnt-work/11698/3 "2020-02-04T12:42:56Z")

</div>

> [@moodagent](#):
>
> Firebase dSYM Upload

Hi @moodagent,

This is a community created step, not one that is maintained by the tooling team. Please add an issue on the repo or send in a pull request on [GitHub - andrewmarmion/bitrise-step-firebase-dsym-upload: Upload your iOS dSYMs to Firebase using CocoaPods](https://github.com/andrewmarmion/bitrise-step-firebase-dsym-upload).

Thanks and happy to answer any other questions.

Kind regards,  
Luna

---

<div class="post-metadata">

**Author:** ![vamsicura](https://avatars.discourse-cdn.com/v4/letter/v/6de8d8/32.png) [@vamsicura](https://discuss.bitrise.io/u/vamsicura)\
**Post date:** [February 17, 2020, 10:48am UTC](https://discuss.bitrise.io/t/firebase-dsym-upload-step-doesnt-work/11698/4 "2020-02-17T10:48:17Z")

</div>

Firebase is disabling the manual upload by March 1st. Can the support to upload dsym using fabric api key be done before that ?

---

<div class="post-metadata">

**Author:** ![kylebrowning](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/kylebrowning/32/2589_2.png) [@kylebrowning](https://discuss.bitrise.io/u/kylebrowning)\
**Post date:** [February 19, 2020, 3:14pm UTC](https://discuss.bitrise.io/t/firebase-dsym-upload-step-doesnt-work/11698/5 "2020-02-19T15:14:11Z")

</div>

If you’re using BitCode, the dsyms uploaded from your build on Bitrise are virtually worthless and you need to download the ones provided by AppStoreConnect.

---

<div class="post-metadata">

**Author:** ![vladimirbakalov](https://avatars.discourse-cdn.com/v4/letter/v/ecb155/32.png) [@vladimirbakalov](https://discuss.bitrise.io/u/vladimirbakalov)\
**Post date:** [February 24, 2020, 9:23am UTC](https://discuss.bitrise.io/t/firebase-dsym-upload-step-doesnt-work/11698/6 "2020-02-24T09:23:13Z")

</div>

Do you know of a nice way of automating that action?

---

<div class="post-metadata">

**Author:** ![kylebrowning](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/kylebrowning/32/2589_2.png) [@kylebrowning](https://discuss.bitrise.io/u/kylebrowning)\
**Post date:** [February 24, 2020, 9:17pm UTC](https://discuss.bitrise.io/t/firebase-dsym-upload-step-doesnt-work/11698/7 "2020-02-24T21:17:36Z")

</div>

`fastlane refresh_dsyms`

it downloads them from iTunes connect, and uploads them to Crashlytics.

Keep in mind though, this needs to be done after processing.

---

<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:** [March 25, 2020, 9:17pm UTC](https://discuss.bitrise.io/t/firebase-dsym-upload-step-doesnt-work/11698/8 "2020-03-25T21:17:38Z")

</div>

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