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

Solution 1

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. May be some issues are there is Firebase Crashlytics upload process!

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

Solution 2

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.

Solution 3

I had the same problem. What I found:

1. 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.
2. On my practice, the delay is usually several mins, max 24 hours.
3. 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.

Comments

[Ashish Kakkad]

Thanks but, I already checked the documents for this... This is not the issue that I am talking :)

[Oleg Kodysh]

Your issue might be related to this github.com/firebase/firebase-ios-sdk/issues/5327

[Ashish Kakkad]

I have downloaded dSYMs from Apple.

[Zubair]

Do you have any open case/ticked AT Fabirc or Firebase Support ?

[Ashish Kakkad]

no... as I posted in answer it has taken almost one day to process...

[Zubair]

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

[Ashish Kakkad]

Are you sure? Do you have any documentation for this time of 24 hours?

[drasick]

I cannot find this message on Firebase documentation, Is still relevant?

[Oleg Kodysh]

@drasick firebase.google.com/docs/crashlytics/…

[drasick]

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

[Oleg Kodysh]

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

[Ashish Kakkad]

This issue is already fixed. Please check my answer. The issue was there at firebase...