Just a quick post to tell everybody that I just added Flurry crash analytics to my app and it's pretty great. I really can't think of any reason not to use this - it is the easiest SDK to integrate on the planet and it will give you detailed information every time a user experiences a crash Seriously, adding the SDK is as simple as this (in app_Delegate.m) ---- #import "Flurry.h" then in didFinishLaunchingWithOptions ----- [Flurry setCrashReportingEnabled:YES]; [Flurry startSession:@"YOUR_SDK_KEY"]; That's it! And look at all of the details you get by adding those three lines of code - https://www.dropbox.com/s/4fo9leffsz7wqfx/Screen%20Shot%202014-02-03%20at%2011.21.21%20PM.png - (geez, I have a lot of crashes..I should probably look into those) There's nothing worse than having users complain about crashes and having no idea what's causing it. This pretty much makes that a problem of the past

Thanks for taking your time to post this Absentia! That's great info and I was just looking for that. :) I have just finished my first Android app (v3) and it crashes sometimes. One question if I may, I am trying to also integrate the analytics following this tut.: https://www.dropbox.com/s/a5exvttrrcxb9u8/12-12%20Flurry%20Android%20Installation.pdf It says to "Add this code to your activity_base.java file" but it is not in my project. Is it now called something else "MainActivity.java"? Thanks, Farcat

Oh man, you are asking the wrong guy haha...I don't know a single thing about developing for Android. Hopefully somebody else will chime in and help you out

Ha ha, no worries. I got overexcited when I was just starting a post about Flurry and saw yours on the forum. Thankfully my IOS apps don't seem to crash that much (or so I think) but since it's so easy I'll install the Flurry crash analytics on my next update. As for my question I'll start another thread as it is not relevant. Thanks, Farcat

Thanks bud, got me scared now. Apps crash? Really? Hahaha :-) Next tip we need is how to ferret out the cause of the crashes. That report is not too helpful at first glance. By the way, what's the meaning of the redacted items? I wonder if your other included SDKs contribute to the crashes. Thanks for sharing and keeping us informed. Keep the faith, stay away from that green creature. :-) -- Niraj

Actually that's what's so cool about it - it does provide detailed info on each crash when you click the link (guess I could've mentioned that in the first place) here's an example of one of those redacted item crashes..no idea what it means but it look like Scringo is causing it somehow - https://www.dropbox.com/s/9c4kuey33l10dd3/Screen%20Shot%202014-02-04%20at%204.39.28%20PM.png You can even download a file which gives you a whole other load of info about it - https://www.dropbox.com/s/se1h4znnpjun8sh/crashReport

You've kind of validated my point about the other SDKs being a cause of crashes. For those situations, you are at a dead end with no solution until they wake up and fix it on their end? (If at all) The second report was also not helpful to this layman. Is Crashlytics truly helpful or is it a case of too much information? Curious ...

In the case of these crashes I can't really decipher a word of it either, but I would say it is definitely helpful for me to know what's going on on the user end Honestly, as of right now I haven't received any negative reviews as a result of these crashes so I'm not really stressing over them too much. But if I did want to resolve the issue I could simply pass the crash log along to Scringo's much more capable team of coders