[31merror: could not complete submission of dSYM at /Users/XXUSERXX/Library/Developer/Xcode/DerivedData/ProjectName-flcoueeibbfifebpxptgzctdsqel/Build/Intermediates.noindex/ArchiveIntermediates/ProjectNameAlpha/BuildProductsPath/ProjectNameAlpha-iphoneos/ProjectName.app.dSYM:
Error Domain=com.crashlytics.mac.error-domain.process-dsym Code=4 "This version of OSX is not able to perform the necessary dSYM transformations."
UserInfo={NSLocalizedFailureReason=This version of OSX is not able to perform the necessary dSYM transformations.}
[0m Command PhaseScriptExecution failed with a nonzero exit code
** ARCHIVE FAILED **
I'm getting the above error message when I upgraded my MAC Mini (Catalina) latest (16 GB RAM) and XCode to latest version.
I'm working with Jenkins to run test cases for IOS and ones test cases are generated then it will get uploaded to Sonar Qube server.
Things Which I've tired.
Restarting MAC mini, Closed XCode, Checked XCode configuration like "Debug information format" set to Yes,"Debug information format" to "DWARF with dSYM file".
Earlier it was working fine after update it is not generating the build, Fastlane is not installed.
Thanks
Upload the dSYM File to AppDynamics Using the UIFrom the Mobile App menu, click Configuration. Click Mobile App Configuration >. From dSYM Mappings, click Upload dSYM package file for iOS crashes. From the XCode dSYM package upload dialog, click Choose File.
Xcode Debugging Symbols(dSYM) dSYM ) which contains a mapping information and with which you can, for example, decode a stack-trace into readable format.
A dSYM file is an ELF file that contains DWARF (debugging with attributed record formats) debug information for your application. DWARF is a debugging file format that supports source-level debugging.
Your version of the Fabric pod is not able to handle symbols from the latest version of MacOS. You'll want to update to the latest pod version (1.10.2 as of 10/21/2019). You may need to sudo gem install cocoapods
, pod repo update
, pod cache clean
, target the newer versions in your Podfile (see next paragraph), and pod update
.
I had v1.9.0 of the pod and was getting the same error. I had to target '~> 1.10' specifically or it wouldn't update. Since my project also includes the Crashlytics pod, I had to update that one as well ('~> 3.14', specifically).
Build, profit. Best of luck!
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With