Mike from Cloth.
Using a bitcode will definitely make this problem more frequent, but there are several ways to handle it. You can automatically download dSYM using Fastlane.tools by running fastlane refresh_dsyms , which will download dSYM from iTunesConnect and then load them into Fabric. The link for Fastlane refresh_dsyms is here: https://krausefx.com/blog/download-dsym-symbolication-files-from-itunes-connect-for-bitcode-ios-apps
In practice, create a fastlane named: refresh_dsyms with the following:
lane :refresh_dsyms do download_dsyms
which will download dSYM from iTunesConnect and load them into Fabric.
Alternatively, you can run the Fabric upload_symbols script, but you will need to manually download dSYM from iTunesConnect - this will only handle the download. The command will be as follows: find <directory-to-search-for-dsyms> -name "*.dSYM" | xargs -I \{\} /path/to/upload-symbols -a <api-key> -p <platform> \{\} find <directory-to-search-for-dsyms> -name "*.dSYM" | xargs -I \{\} /path/to/upload-symbols -a <api-key> -p <platform> \{\}
The link for upload_symbols is here: https://docs.fabric.io/ios/crashlytics/missing-dsyms.html#upload-symbols-script and
For this reason, Apple will recompile your application when the bitcode is turned on, so dSYM is generated only on Apple servers, which prevents Fabric from loading automatically.
source share