Same issue here.
It seems as if appstoreconnect currently attributes incorrect UUIDs to dsyms generated from bitcode enabled build archives.
One way to solve this (and the only one I know of) is to rename the internal UUID of the dsym that corresponds to the binary image of the stack frame that isn't symbolicated. In most cases this is your app's binary image.
What you can do is either manually rename it using the already mentioned excellent article on medium, or automatically using the following tool: https://github.com/schmittsfn/dsymrename
You have to be absolutely sure, however, that the dsym you are renaming corresponds to the build Crashlytics is requesting (for bitcode builds these are the dsyms generated on appstoreconnect)! Failure to do so will most likely lead to the warning on Crashlytics being silenced and the stack frame being unintelligible.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags: