Firebase Upload missing required dSYMs Not Working

Question

Currently, I am facing issues to upload dSYMs through the new uploader script.

/path/to/Fabric/upload-symbols -gsp /path/to/GoogleService-Info.plist -p <platform> /path/to/dSYMs

I am getting success response by uploading the dSYMs

But no change on firebase console.

I have already checked the following thread:

https://github.com/firebase/firebase-ios-sdk/issues/5327

Please let me know if anyone having a solution...

Please use [tag:google-fabric] tag, because [tag:fabric] is unrelated to your question, it is about python library. Take a look at the description of the tag — Vadim Kotov, Apr 16 '20 at 10:10
@Ashish kakkad have u uploaded dsym through run script in build phases ? are u getting the crashes in firebase console. — iMinion, Jun 19 '20 at 15:39

Ashish Kakkad · Accepted Answer · 2022-08-01T09:22:55.287

2

Don't know what is going on in the Firebase Crashlytics.

But after 1 Day/24 Hours the dSYMs processed and now they are showing (Optional) in the same build.

Update

I have again uploaded the dSYMs today, and it uploaded quickly. Maybe some issues are there with the Firebase Crashlytics upload process!

https://github.com/firebase/firebase-ios-sdk/pull/5228

edited Aug 01 '22 at 09:22

answered Apr 16 '20 at 06:02

Ashish Kakkad

23,586
12
103
136

score 1 · Answer 2 · answered Apr 15 '20 at 19:10

1

If this is a migrated app from Fabric, then you need to follow these directions,

"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."

If this is not a migrated app, and you're seeing that the correct missing UUID is being uploaded, but you're still getting the missing dSYM error, then you need to write into Firebase Support so they can get your debug logs and check your session ID.

answered Apr 15 '20 at 19:10

Oleg Kodysh

986
6
13

Thanks but, I already checked the documents for this... This is not the issue that I am talking :) – Ashish Kakkad Apr 16 '20 at 06:16
Your issue might be related to this https://github.com/firebase/firebase-ios-sdk/issues/5327 – Oleg Kodysh Apr 16 '20 at 20:28
I cannot find this message on Firebase documentation, Is still relevant? – drasick Jul 22 '20 at 12:39
@drasick https://firebase.google.com/docs/crashlytics/upgrade-sdk?platform=ios#the_run_and_upload-symbols_scripts_are_now_in_firebasecrashlytics – Oleg Kodysh Jul 22 '20 at 14:16
@OlegKodysh I cannot find this in the documentation "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." It actually said to move towards using FirebaseCrashlytics and do not mention if thee app is migrated or not. – drasick Jul 23 '20 at 21:25
@drasick that's the updated documentation. What I wrote above in my answer only applies if you migrated from Fabric, and linked your app into Firebase. This is no longer possible to do, so if you haven't already done it, then no need to worry about it. – Oleg Kodysh Jul 24 '20 at 13:34

score 1 · Answer 3 · answered Jul 15 '21 at 02:48

I had the same problem. What I found:

You should double-check if you can find this specific DSYM in your XCode archive. For this, open XCode->Organizer->Show In Finder-> DSYMs in bundle: try to find specific DSYM by ID from the dSYMS error Firebase panel. If any you can find with the same ID, you have to upload manually.
On my practice, the delay is usually several mins, max 24 hours.
Sometimes, I couldn’t find the DSYM IDs listed on Firebase in XCode archive or from AppStore downloads. What I found, that Firebase catches all distributed versions of the app. That’s why you cannot find them on AppStore if it is not on TestFlight yet. You probably can find them in your alpha archives.

However, this is my guessing. I was wondering if anyone from Firebase guys can give more info on this.

score 1 · Answer 4 · answered Feb 19 '22 at 05:43

install crashlytics via POD 'Firebase/Crashlytics'. download DSYMS from app store. located here --> myapps --> select your app --> testflight --> select latest build --> Build Metadata --> Download dSYM.

now run this script using Terminal directly

YOUR PROJECT POD FOLDER PATH /FirebaseCrashlytics/upload-symbols -gsp /YOUR PROJECT/GoogleService-Info.plist -p ios /Users/username/Downloads/appDsyms

more in detail step.

Open terminal, drag and drop 3 files on terminal on this order:

A--> drag an drop: "upload-symbols" which can be found in /project/Pods/FirebaseCrashlytics/upload-symbols

B--> write " -gsp "

C--> drag an drop: "GoogleService-Info.plist" which can be found in /project/GoogleService-Info.plist

D--> write " -p ios "

E--> drag an drop: "appDsyms" folder (unarchived, zip file might not work!) which usually is in Download folder /Users/username/Downloads/appDsyms

F--> Press Enter

In terminal the complete command should include -gsp and -p ios, full command looks like this: A -gsp C -p ios E

/project/Pods/FirebaseCrashlytics/upload-symbols -gsp /project/GoogleService-Info.plist -p ios /Users/username/Downloads/appDsyms

it might take some time to reflact on google firebase 24 hours.

This issue is already fixed. Please check my answer. The issue was there at firebase... — Ashish Kakkad, Feb 21 '22 at 04:54

Zubair · Answer 5 · 2020-04-17T19:35:57.460

0

Currently, it is taking (around) 24 hr to process the dSYMs (specially, if dSYM size is large), but it should improve soon.

Most Impacted Developers:

Fabric legacy only, not migrated customers - should no see impact
Fabric legacy SDK, migrated to Firebase - impacted
Fabric legacy SDK, onboarded via Firebase - impacted
Firebase SDK (currently in beta) - no impact

It is suspected that the dsym downloaded from Apple has the incorrect bundle id. Apple is setting com.apple.xcode.dsym. (e.g. com.apple.xcode.dsym.Bingo Blast).

1- As a temporary workaround, if the developer after downloading the dsym from Apple, converted all occurrences of the incorrect bundle string with the correct bundle id (e.g. com.redhotlabs.bingo), this should allow the dsym to be ingested correctly.

See an example shell script that developers could use replacing the and with the appropriate values.

export BUNDLE_ID='' export DSYM_PATH='' sed -i '' -e "s/>com.apple.xcode.dsym.*\$BUNDLE_ID\

2- Try not test-crash the app or release a potentially crashy app to users for at least 10 minutes after upload-symbols has completed and the mapping file is uploaded.

3- I would recommend to upgrade to Firebase SDK (currently in beta) to avoid this issue all to gather.

edited Apr 17 '20 at 19:35

answered Apr 17 '20 at 11:02

Zubair

525
4
13

I have downloaded dSYMs from Apple. – Ashish Kakkad Apr 17 '20 at 11:26
Do you have any open case/ticked AT Fabirc or Firebase Support ? – Zubair Apr 17 '20 at 11:45
no... as I posted in answer it has taken almost one day to process... – Ashish Kakkad Apr 17 '20 at 11:48
Currently, it is taking (around) 24 hr to process the dSYMs (specially, if dSYM size is large), but it should improve soon. – Zubair Apr 17 '20 at 12:46
Are you sure? Do you have any documentation for this time of 24 hours? – Ashish Kakkad Apr 17 '20 at 14:04

Firebase Upload missing required dSYMs Not Working

5 Answers5