issue with uploading dSYM to crashlytics

If you have bitcode on because you want app-thinning or a TVOS or WatchOS app, then the dSYMs you create when you generate the xcarchive are NOT the dSYMs required. This is because apple re-compiles from the bitcode. To get the real dSYMs, go to itunesconnect, open up the specific (processed) build, and hit the "Download dSYMs" link. Apparently fastlane can automate this process (I have not tried it): https://krausefx.com/blog/download-dsym-symbolication-files-from-itunes-connect-for-bitcode-ios-apps

AFAIK, You install the fabric software on your mac, on which you are making your build or archive, as soon as you make an archive, it automatically asks for your permission and uploads the dsym file.

Also see Fabric Integration Troubleshooting, see 4 point under TroubleShooting

It’s possible, but rare, that we are missing a dSYM to symbolicate any crash reports. There will be an alert on your dashboard if this is the case. Click through to upload the missing dSYM. Keep in mind that exceptions are not guaranteed to crash. The full code path, including code in system libraries, matters here. If you aren’t seeing the dSYM alert, you can go to your app’s settings page, and append “/mappings” to the URL to reach it, e.g. https://fabric.io/settings/apps//mappings

I have created a tool to upload the dSym files:

https://github.com/prsolucoes/fabric-upload-dsym

This tool is open source and made with golang. It can simplify the upload process without any other tool.

Thanks.