symbolicatecrash

I am trying to analyse a crash log that a customer sent me, but I cannot get it to symbolicate the system library calls. It does symbolicate calls to my own methods correctly. That does not make it very practical to analyse what goes wrong. I have run 'symbolicatecrash -v', to see what is causing the lack of symbolication. The likely cause is this: ## /Users/baraupp/Library/Developer/Xcode/iOS DeviceSupport/6.1.3 (10B329)/Symbols/usr/lib/system/libsystem_kernel.dylib doesn't contain armv7s slice I have checked the mentioned libraries with 'lipo', which says that they contain 'armv7' but no

After searching all over the internet to find a way to symbolicate my crash logs I received from Apple, I finally figured out how to use the atos command in terminal to symbolicate the crash logs. I have the dSYM file, the .app file and the crash logs in the same folder, and using atos -arch armv7 -o APPNAME I have been able to enter memory addresses, and sometimes (but quite rarely) a method name has come up. To be perfectly honest, I don't have much experience with terminal, or crash logs. Attempting to symbolicate the crash logs from Xcode's organiser has unfortunately done absolutely

I have a user who is experiencing a crash using the app store version of an iPhone app. The crash is not reported via iTunes connect and the user is unable to sync with iTunes and get me the .crash file (they don't have a computer). The user is, however, able to copy and paste the crash report from the phone under "Settings > general > about > Diagnostics & usage data". I took this users copied crash report and manually pasted it into a text file and renamed it with the .crash extension. When I import this manually created .crash report into XCode's Organizer, I am not able to symbolicate it.

I'm trying to get XCode 4 to symbolicate a crash report. I've googled and followed this link (https://github.com/chrispix/symbolicatecrash-fix) but get stopped. The instructions say "To fix your iOS crash report symbolication, move /usr/local/bin/symbolicatecrash aside and copy in the version in this repo." Well, I cannot find "/usr/local/bin/" on my Mac. I'm new to the Mac world, so I'm sure there's something I'm not understanding. If "/usr/local/bin/" doesn't exist, then where is XCode 4 finding symbolicatecrash? Please point a newbie in the right direction as I have a lot of bugs to be

I should have the symbolicate from my device. I followed the instruction from http://jmillerdev.net/symbolicating-ios-crash-files-xamarin-ios . I created the alias for Xcode 8 alias symbolicate="/Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources/symbolicatecrash -v" I updated the developer directory export DEVELOPER_DIR="/Applications/Xcode.app/Contents/Developer" and then the symbolicate symbolicate -o "symbolicatedCrash.txt" "MyAppName 2-12-14, 9-44 PM.crash" "MyAppName.app" but I have an error Symbolicating myInventories170313.crash ... while

My app got rejected from Apple and I have got crash reports in .txt format instead of .crash format. How can I symbolicate or read the crash report ? Shakti When you get your crash report as a .txt file just follow these steps : Change the file extension .txt to .crash (eg mycrash.txt to mycrash.crash ). Create a new folder in desktop and copy the mycrash.crash file to the newly created folder. Copy the .dSYM file: update: download all DSYMs from appstoreconnect activity- they are properly named with their UUIDs Unzip DSYMs, then copy the App and Sybolicate script as defined below: https:/

The new Xcode 7 "Crashes" tab in the organizer shows a handful of crashes from the AppStore for my app. According to the documentation , there should be a stack trace. However, none of the 6 crashes have symbolicated stack traces: I've tried clicking "Open in Project" but it's just as useless: Of course, I included the dsym and debug info when I submitted to the store. I still have the submission build in my organizer, so the dsyms are still present on my machine. How can I get a proper stack trace on this? esilver Not ideal, but if you right-click an .xccrashpoint file, select "Show Package