IOS-capture application crash logs, ios-capture logs

IOS-capture application crash logs, ios-capture logs
As an iOS mobile app developer, to ensure that your app is correct, you must perform a lot of testing before submitting the app to the app store; in addition, the application program runs well during your test. However, after the App Store is launched, some users complain that the application will crash "! Now, as a developer of the application, you are sure to open the code and prepare to fix the problem of "crash". But at this time, you will find that the code exactly exists? Where is the problem ......; at this time, the iOS Crash log comes in handy. Now we will study how to obtain the application crash log and track the code from the log. (1) What is a crash log and Where can it be obtained: When an application on the iOS device returns, the operating system will generate a crash report, also known as a crash log, which is stored on the device, there is a lot of useful information on the crash log, including when the application is crashed. Generally, there is a complete stack trace information for each thread being executed, so you can find out what each thread is doing when a crash occurs, and identify the thread on which the crash occurs. (2) several methods for obtaining crash logs: 1. When a user complains about a crash, you can ask him to synchronize the device with iTunes, and after the device is synchronized with the iTunes Store on the computer, will Save the crash log on the computer (Path: Mac OS X :~ /Library/Logs/CrashReporter/MobileDevice/) download the crash log and send it to you by email, you must obtain all crash logs generated by your device whenever possible. The more crash logs, the easier it is to diagnose the problem. 2. If you have installed Xcode, you can easily get the crash log from your device through Xcode. Connect the iOS device to your computer and open Xcode. Select the Window menu from the menu bar, then select Organizer (shortcut is Shift-CMD-2) in the Organizer window, select the Devices tab, and on the left-side Navigation Pane, select Device Logs; the Device Logs under the LIBRARY is the log of all your devices (once connected to Xcode); the Device Logs under each Device is the log of the corresponding Device. 3. After the application is submitted to the App Store, you can also get the user's crash log from iTunes Connect, log on to iTunes Connect, select Manage Your Applications, and click the corresponding application, click View Details under the application icon, and then click Crash Reports in the Links section on the right. If no Crash logs exist, Click Refresh to Refresh the page. If the number of users for your application is not large, or the iTunes Connect account has not crashed before the installation, you will see crash information for users of different iOS versions. 4, the use of tools to get the application crash log, now xiaobian to recommend a good tool (Name: buugly, URL: http://bugly.qq.com/) on the official website by a detailed explanation, with Demo, I will not explain it one by one. 5. The iphone crash log analysis tool symbolicatecrash; The Symbolicatecrash is an analysis tool that comes with Xcode, which can be used by crash logs and applications on the machine. the dSYM file located the location where the crash occurred, replacing the address in the crash log with the corresponding location of the Code (see the http://www.cnblogs.com/ydhliphonedev/archive/2012/12/07/2806866.html for details); (3) What will cause the crash log: 1. user violation of operating system rules: violation of iOS rules includes watchdog timeout during startup, recovery, suspension, and logout, user forced logout, and low memory termination. 2. There is a Bug in the app: At this time, everyone will think that the app with the Bug will upload the App Store successfully? The small Editor understands that some of the potential bugs in the application may be bugs generated after the iOS system is updated. Just think about iOS8-> after iOS9, Apple silently changed http to https. (The above is the introduction and understanding of capturing application crash logs, and we hope you can complement each other for common progress)