Tuesday, June 26, 2012

Sending Crash Logs to iOS Developers

I've lately met some problems with a remote peer testing an application that I'm developing and unfortunately he gets some crashes. I recently found a way for non-geeky testers to send crash logs to developers. Quoted from Apple's guide

Sending Crash Reports to a Developer

When the app you’re testing crashes, iOS creates a record of that event. The next time you connect your device to iTunes, iTunes downloads those records (known as crash logs) to your computer. To help get the problem fixed, you should send crash logs of the app you’re testing to its developer.
Sending Crash Reports from Macs
To send crash logs to developers:
  1. In the Finder, open a new window.
  2. Choose Go > Go to Folder.
  3. Enter ~/Library/Logs/CrashReporter/MobileDevice.
  4. Open the folder identified by your device’s name.
  5. Select the crash logs named after the app you’re testing.
  6. Choose Finder > Services > Mail > Send File.
  7. In the New Message window, enter the developer’s email address in the To field and <app_name> crash logs from <your_name> (for example, MyTestApp crash logs from Anna Haro) in the Subject field.
  8. Choose Message > Send.
  9. (Optional) Delete the crash logs you sent, to avoid sending duplicate reports later.
Sending Crash Reports from Windows
To send crash logs to developers:
  1. Enter the crash log directory for your operating system in the Windows search field, replacing <user_name> with your Windows user name.
    • For crash log storage on Windows Vista
      C:\Users\<user_name>\AppData\Roaming\Apple computer\Logs\CrashReporter/MobileDevice
    • For crash log storage on Windows XP
      C:\Documents and Settings\<user_name>\Application Data\Apple computer\Logs\CrashReporter
  2. Open the folder named after your device’s name and send the crash logs for the app you’re testing in an email message using the subject-text format <app_name> crash logs from <your_name> (for example, MyTestApp crash logs from Anna Haro) to the app’s developer.

0 comments: