{"action":"opened","issue":{"number":62,"created_at":"2011-10-26T14:11:38Z","pull_request":{"diff_url":null,"patch_url":null,"html_url":null},"body":"In my app, I have certain error scenarios that I can detect, but can't recover from (mostly core data save failures).\r\n\r\nFor now, I can abort() to save the crash info at the point of failure, but this isn't very user friendly.  I would like to save the backtrace info at the point of failure, then exit gracefully by displaying a modal dialog that a crash occurred and to press home to exit.  Either after the next time the user starts the app, or before the user presses home, I'd like QuincyKit to send the backtrace.\r\n\r\nIs there any way to save the crash info without actually crashing?\r\n\r\n","comments":0,"title":"Can I force saving crash info without actual crash on iOS?","updated_at":"2011-10-26T14:11:38Z","url":"https://api.github.com/repos/TheRealKerni/QuincyKit/issues/62","id":2057001,"assignee":null,"milestone":null,"closed_at":null,"user":{"gravatar_id":"fa241117f52eb7075a045f8938b1497e","avatar_url":"https://secure.gravatar.com/avatar/fa241117f52eb7075a045f8938b1497e?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","url":"https://api.github.com/users/jamusj","id":42900,"login":"jamusj"},"html_url":"https://github.com/TheRealKerni/QuincyKit/issues/62","labels":[],"state":"open"},"legacy":{"number":62,"action":"opened","issue":2057001}}