dsym file

I have not been able to find much chatter at all about the impact of not having dsym files via TestFlight to support Crashlytics reporting. Currently, I download the files from TestFlight and then upload them to Firebase. Then, a Slack integration is used to notify me when there is a new crash that needs to be investigated. Does the new change to XCode 14 basically remove Crashlytics from equation? Since I rely on Apple to sign the apps, I'm assuming that nothing local can be used. But, I'm also still learning. Any insights/suggestions are appreciated.

I'm trying to debug a couple of crash reports for a Mac Catalyst app and seem to be unable to symbolicate my crash reports. In the Xcode Organizer, I see unsymbolicated lines for my app, despite having the original archive for the build in question. A search for the relevant dSYM (using the process from https://developer.apple.com/documentation/xcode/adding-identifiable-symbol-names-to-a-crash-report#Locate-a-dSYM-Using-Spotlight) yields no results. Unlike iOS builds, the Download dSYMs button isn't present in the organizer, nor is the option to download dSYMs from App Store Connect. I assume this is because macOS apps don't use bitcode. The app's Debug Information Format is set to DWARF with dSYM File. Has anyone else run into this issue? Any ideas about how I can symbolicate the crash logs?

Hello Folks; I'm trying to utilize a crash log from App Review. I've uploaded the app with DWARF with dSYM File. When I open the App Review .crash file in Xcode I see this: #0 in __pthread_kill () #1 in pthread_kill () #2 in abort () #3 in abort_message () #4 in demangling_terminate_handler() () #5 in _objc_terminate() () #6 in std::__terminate(void (*)()) () #7 in std::terminate() () #8 in _dispatch_client_callout () #9 in _dispatch_main_queue_callback_4CF () #10 in __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ () #11 in __CFRunLoopRun () #12 in CFRunLoopRunSpecific () #13 in RunCurrentEventLoopInMode () #14 in ReceiveNextEventCommon () #15 in _BlockUntilNextEventMatchingListInModeWithFilter () #16 in _DPSNextEvent () #17 in -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] () #18 in -[NSApplication run] () #19 in NSApplicationMain () #20 in 0x10a062000 () #21 in 0x10a062000 () #22 in start () Whereas in Console it looks like this: 0 CoreFoundation 0x00007

I have Mac OS application with several embedded frameworks. When debugging the application in recent versions of Xcode (comfirmed in 14.2) I am no longer able to inspect opaque C structs defined in a framework when the debugger has stopped in code belonging to the application or a different framework. The application and frameworks are all compiled by me as part of the application workspace, all have debugging enabled, and all are properly generating dSYM files. Does anyone know what might be going on? This is making debugging the framework code very difficult.

I need to retrieve current crash logs for the build, which is in App Store or symbolicate crash logs from devices for this build. All builds were sent from another machine, so i do not have them. In iTunesConnect i can't neither download any build nor download dSYM file (Includes Symbols is set to YES).Is there any way to view current crash logs?P.S: Please, do not suggest any solution like Crashlytics, because i need current crash logs, that should be already saved in iTunesConnect.

When I first ran the allocations tool, the call tree didn't display any user functions. After reading the Instruments User Guide, I change my app's build settings / debug information format from DWARF to DWARF with dSYM File. This had the following effects:1. The allocations tool displayed user functions.2. Clicking File / Symbols displayed a dialogue where: a. A yellow-colored dot preceeds liboainject.dylib (In this view, Binary Path has red-colored text.) b. A green-colored dot proceeds (App Name) (In this view, Binary Path and dSYM Path look reasonable.) c. Disclosure triangle (My App Name) (In this view, Binary Path is blank.)Are the indicators correct for using tools requiring the dSYM path?What is liboainject.dylib?When I changed the DWARF settings it changed both debug and the release. Should I refine this by setting release to DWARF?Thank you.