symbolicatecrash

I am trying to use the new Xcode 7 feature that shows crash report directly into Xcode. It is working well with my AppStore live version. But when trying to open crash report from my latest TestFlight build, it does not symbolicate, so I can't find the method name of the given crash. Any clue on how to solve this ? Thank you 来源： https://stackoverflow.com/questions/33169275/xcode-7-does-not-symbolicate-testflight-crash-report

This is not a question because I have already found a workaround. I am publishing it so that others can take advantage on the hours I was spending on it, and use my suggested workaround. I have got some strange crash reports - a single line was duplicated many times: ... 0x190e08000 - 0x190e49fff Notes arm64 <f45c09ce977b3282ab0e879252dfebee> /System/Library/PrivateFrameworks/Notes.framework/Notes 0x190f9c000 - 0x190fa6fff NotificationsUI arm64 <73dcb247ed183ce7bb330d7bb55f93bd> /System/Library/PrivateFrameworks/NotificationsUI.framework/NotificationsUI 0x190fa8000 - 0x190faafff OAuth arm64

I have an app which is written in swift and uses AFNetwork and some other helpers written in Obj c. On my clients device (iPhone 6+) he is getting an SIGTRAP error, I have tried to recreate the issue on the testing devices that we have and on all the simulators but could not recreate it. Below is the stack trace, it crashed twice: http://paste.ubuntu.com/12077304/ When I symbolicate the crash report it is pointing to: -[Instagram getOwnBaseUrl] (in DiaryApp) (Instagram.m:118) And on the second instance it point to: [UIAlertView(AFNetworking) showAlertViewForTaskWithErrorOnCompletion:delegate

I just upgraded my xcode to version 4.5, I tried three ways for symbolicating crash log, but neither of them success. Firstly, I got the crash log from my device and then imported it into "Device Logs" of Organizer, but the exact function of my app cannot be displayed, the memory address still displayed in result. Secondly, I copied the 'symbolicatecrash' file from '/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/PrivateFrameworks/DTDeviceKit.framework/Versions/A/Resources' to '/usr/local/bin' and put the .DSYM file, .app file and .crash file into a

I have got many crash logs from different users, I have different builds and dSYM file now how can i make sure a particular crashlog belongs to which build and dSYM file. Is there is any way to check if both crashlog and dSYM belongs to same build...?? Regards, You have to archive the binary and the dSYM, since every build will create new ones each having an identical UUID. You can use dwarfdump --uuid yourapp.app/yourapp and dwarfdump --uuid yourapp.app.dSYM to check the UUIDs of individual binaries. To search for a dSYM with a specific UUID via Spotlight you can do: mdfind "com_apple_xcode

I can't manage to make my code symbolicated ... I read the part "below" : Given a crash report, the matching binary, and its .dSYM file, symbolication is relatively easy. The Xcode Organizer window has a tab for crash reports of the currently selected device. You can view externally received crash reports in this tab - just place them in the appropriate directory. This is the same as the Mac OS X directory described in the first section. It doesn't matter which device you have tethered, but the directory in which you place the crash report must be the directory for the tethered and selected

I have a crash dump which will not symbolicate normally - when I drag it into the Xcode organizer or manually run symbolicatecrash the system symbols show up, but the application instruction addresses are all untouched. I tried using atos to work around this problem, but the result I got was: got symbolicator for myarchive.xcarchive/Products/Applications/MyApp.app/MyApp, base address 4000 ___lldb_unnamed_function2115$$MyApp (in MyApp) + 992 ___lldb_unnamed_function2096$$MyApp (in MyApp) + 66 ___lldb_unnamed_function6053$$MyApp (in MyApp) + 348 ___lldb_unnamed_function6064$$MyApp (in MyApp) +