xcode 确保您的项目构建设置正在生成 dSYM 文件。对于所有配置，DEBUG_INFORMATION_FORMAT 应设置为 dwarf-with-dsym
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/29209582/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Make sure your project build settings are generating a dSYM file. DEBUG_INFORMATION_FORMAT should be set to dwarf-with-dsym for all configurations
提问by Snowcrash
I've recently started getting this error:
我最近开始收到此错误：
2015-03-23 11:35:48.902 run[60036:1047011] Crashlytics.framework/run 1.3.14
2015-03-23 11:35:48.911 run[60036:1047011]
Crashlytics: dSYM Error
Unable to process <your app>.app.dSYM at path /path/to/<your app>.app.dSYM
Make sure your project build settings are generating a dSYM file. DEBUG_INFORMATION_FORMAT should be set to dwarf-with-dsym for all configurations. This could also be a timing issue, make sure the Crashlytics run script build phase is the last build phase and no other scripts have moved the dSYM from the location Xcode generated it.
Command /bin/sh failed with exit code 1
I tried this answer Unable to copy dSYM file into archivebut all my Generate Debug Symbolsare set to YES
我试过这个答案Unable to copy dSYM file into archivebut my all my Generate Debug Symbolsare set toYES
Any further suggestions?
有什么进一步的建议吗？
回答by ABS
The below solution worked for me ,i hope it will help you.
以下解决方案对我有用，希望对您有所帮助。
Goto build setting of your project then Search for debug information format in build setting and search for "Debug information format" then set "Debug information format" to "DWARF with dSYM file"
转到项目的构建设置，然后在构建设置中搜索调试信息格式并搜索“调试信息格式”，然后将“调试信息格式”设置为“带有 dSYM 文件的 DWARF”
and make sure Generate debug symbolin build setting is set to Yes.
并确保在构建设置中生成调试符号设置为是。
回答by Bruno
Check for true "run script only when installing" on Run Script
在运行脚本上检查“仅在安装时运行脚本”是否正确
回答by chuckSaldana
Elaborating Bruno's response, if you already have a script phase that you need to run all the time, create a new dedicated phase in order to avoid conflicts.
详细说明 Bruno 的回应，如果您已经有一个需要一直运行的脚本阶段，请创建一个新的专用阶段以避免冲突。
回答by Zsolt
I removed Fabric and Crashlytics and added them back again from the beginning just like I were to install it the first time around. It worked.
我删除了 Fabric 和 Crashlytics，然后从头开始重新添加它们，就像我第一次安装它一样。有效。
see also https://twittercommunity.com/t/how-to-reinstall-fabric-crashlytics/37890
另见https://twittercommunity.com/t/how-to-reinstall-fabric-crashlytics/37890
