Search results for

dsym file

77,664 results found

Post

Replies

Boosts

Views

Activity

Reply to App Crash only on App Review
I have Realm source code but I am not sure how to proceed further. OK, let’s see if we can fix that. Looking at your crash report excerpt I see this: 2 Realm … RLMAccessorContext::createObject(objc_object*, realm::CreatePolicy, bool, realm::ObjKey) + 1776 3 Realm … RLMAddObjectToRealm + 264 4 RealmSwift … Realm.add(_:update:) + 279776 … That means that somewhere in the Binary Images section of the crash report there must be Realm and RealSwift binaries. Each of those will have an associated UUID. To symbolicate your crash report you need to find the .dSYM files whose UUID matches those UUIDs. If you built those binaries from source code, the build process should have creating corresponding .dSYM files. If it didn’t, you need to adjust your build settings so that it does. If you use binaries built by someone else, you’ll need to get the .dSYM files from them. You can check you have the right files by matching up UUID, as discussed in Adding Identifiable Symbol Names to a Cra
Jul ’22
Reply to xcode changes dsym bundle identifier
dSYM files never go inside the app bundle. During an archive action in Xcode, dSYM files land in YourApp.xcarchive/dSYMs, so that's where you should expect to be finding this particular dSYM before submitting to the App Store. If that's not the case, it would be helpful to go backwards through your build process to figure out why that's not happening. For example, I'm noticing the path component Resources/Modules/Release/BIS.bundle.dSYM , which makes me think there's a component to your build which is moving entire directories named Modules or Release around which is having unintended consequences here. — Ed Ford,  DTS Engineer
Sep ’25
Reply to Crashed at <compiler-generated> line 0
Yes. I've noticed previously generated dSYM files contains t __T013 instead of t _$S13 and reports for that dSYM file were just Ok. Also ive tried to create a build using Legacy Build System but still without luck for correct symbolication. In addition I have an Apple crash report and I'm not able to navigate to the line of code which cause crash. Screenshots: http://i.piccy.info/i9/56daf8329a3148149632644958c99a66/1543575246/108433/1285538/Screen_Shot_2018_11_30_at_12_52_18_PM.png
Nov ’18
Is there a way we can upload dSYM file when we upload .ipa file to TestFlight via shell script
Command xcrun altool --upload-app -f $ipa_path -u $appstore_connect_username -p $appstore_connect_password If we do it manually using Xcode -> Window -> Organizer then it shows a checkbox (Upload your app's symbols to receive symbolicated reports from Apple) which is checked by default. Since we have automated ipa uploading to testflight using above command, but dSYM is not uploading in that case. How can we upload dSYM to AppStoreConnect automatically? Note: My iOS app project doesn't have bitcode enabled.
4
0
4.9k
Sep ’21
No dSYM files in Apple iTunes Connect Xcode 14.2 Bitcode Disabled
We are building our apps using Azure DevOps and uploading our builds to TestFlight. Azure uses Xcode 14.2 to build our apps and the bit code is disabled. We do not see the Download dSYM button in the Apple iTunes Connect. The build metadata says Symbols Included however there is no button to download the dSYM. Since the app was built using Azure we do not have access to the archive file. Please help.
0
0
495
Jul ’23
Reply to Absent Method Calls in Instruments Stack Trace
The issue was due to a .dSYMM file generated by XCode as part of the build. The file is used in debug mode to symbolicate method calls. Instruments doesn't seem to be aware of its location. In order to fix that I had to do the following:Before starting to record under Instruments, go to File->SymbolsUnfold your app item and select your app nameClick Locate in front of dSYM paththe dSYM file corresponding to the app should be under ~/Library/Developer/Xcode/DerivedData/Build/Products/Debug-iphoneos/[APP_NAME].app.dSYM.A dialog should pop up asking you whether Instruments should always look for dSYM files under that location; that's what you wantStart recording; your method calls should now display properly
Jul ’15
Reply to Exception SIGABRT encountered in App Store review
Do you think the reason I am unable to further symbolicate the .ips file is because I do not have the correct .dSym file? The Binary Images section of the .ips file is as shown below. Where is the required UUID? Can you tell me how to use dwarfdump to see if I have a .dSYM with the right UUID and how to use mdfind to see if it is visible to the symbolicator and what to do if it is not?
Topic: App & System Services SubTopic: General Tags:
Jul ’22
Empty dSYM file detected & Error: type for self cannot be reconstructed: type for typename
I'm pulling my hair out here with this new Xcode 16, it complains that my app's dSYM is empty though it's clearly not, it's about 25MB. I'm working on a project using an internal static library, everything is built inhouse using swift, we own all the source code. It worked just fine until the other week, when I updated the Xcode, and now I can't debug anything. I keep getting type for self cannot be reconstructed when I run po self.some_property. Why is that? The Debug information Format is set to DWARF with dSYM File for both the executable and lib projects. I've been a Unix guy since before I knew myself and I enjoy fixing things myself, down to bare metal, but man, this bug is driving me crazy. Is it even a bug?? It's the first time in more than 15 years since I started coding on Mac and iPhone when a bug has defeated me. I was always able to fix things using just the documentation and google, but the Apple toolchain is getting worse and worse nowadays. I remember the time when Apple made
1
0
1.1k
Jan ’25