seen from Ukraine
seen from Singapore
seen from Germany
seen from Saudi Arabia
seen from Uruguay
seen from United States
seen from United Kingdom
seen from Germany
seen from China
seen from China
seen from Germany
seen from South Africa
seen from United States
seen from Germany
seen from United States
seen from United States
seen from China
seen from United States
seen from Uruguay
seen from Türkiye
Great introduction to crash reporting basics on iOS, including symbolication, and also a comparison of different crash reporting services.
Using a crash reporting service is a must - you can be notified of crashes in real time, and not have to wait for a user to report them (which they may never even do). Lets you get an update out that much faster, meaning lesser chances of a bad review.
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
Managing iOS Crash Reports with PLCrashReporter
I often hear that when your product grows so big you need to assess and prioritize bugs based on the amount of reports per bug you get. (I do hope that you’ll never have too many bugs and need to prioritize them!)
This is how we currently manage bugs:
Bugs are caught by PLCrashReporter. I’ve got a fork somewhere as well for Lion + Xcode 4 + iOS targets.
I’ve got an UIApplication+CrashReporting accessory in IRFoundations/IRAccessories which does all the work in the iOS app.
Most iPads and iPhones have email accounts set up, so it is used for reporting.
Emails are then sent to a shared email account, and Redmine is set up to fetch all of them, which are converted to actual tickets in a special project.
We run a forked PLSymbolicate which relies on gem ruby_protobuf and spotlight.
