Debugging stack trace - windows-phone-7.1

My application for windows phone uses Microsoft Ad SDK and recently I have noticed a lot of crashes in the application which I feel has something to do with the Ad SDK/control. The stack trace provided by the App Hub for the app can be accessed from here.
Any idea what is causing the crash?

By the stack trace I think you have the same problem that this guy had:
http://windowsphonegeek.com/articles/Handling-AdControl-Fetching-Exception

Related

get Error or stack trace from an app crash iOS

hi i want to know the error from a crash of my app in production, I figured out how to recognize if my app crashed during last time execution with crashlitycs but I want the error or the stack trace for send it to a service of my own with user feedback.
is there a way to obtain this error or stack trace with crashlytics, another package or native solution?
thanks

Reporting app crashes: PLCrashReporter vs uncaughtExceptionHandler

I need to send app crashes stacktraces to a certain web service (I was given such requirement). It looks like there is a third-party framework, PLCrashReporter, that allows to send such info to the web service you want, is that right?
On the other hand, I've read that it is also possible to get the app crash info in an uncaughtExceptionHandler method, to write it to a file, and send it when app launches again, is that also right?
After reading a little about both options, I have some questions. I just want to send crashes info to my particular web service, so:
Is integrating PLCrashReporter worth to do only what I need?
Is such functionality of PLCrashReporter under the MIT license? And will Apple approve it for release in App Store? My app will be a commercial one.
Is there any other crash reporting framework I could use to call my own web service?
Regarding uncaughtExceptionHandler, I read somewhere that it is not reliable to report app crashes this way, is that correct?
Thanks in advance
Yes.
It's fine. I've been using it for years in my commercial iOS apps.
Such questions are off-topic.
Use PLCrashReporter - it does all the hard stuff for you.

Retrieve Crash Reports and Logs in Objective C

I have released my application in App store. How to trace the error logs and crash report happened from the end user? Is the NSLog or NSException in the code to find the trace?
Can you please advice on how to implement in the code logic to trace the logs efficiently ?
Is there any open source API Available to trace the logs in the application ?
Here are the ways to integrate the open source api to analyze the Crash Report Logs in IOS :
JIRA Mobile Connect Reference (Open Source) :
https://developer.atlassian.com/display/JIRADEV/JIRA+Mobile+Connect
https://developer.atlassian.com/display/JIRADEV/JIRA+Mobile+Connect+FAQ#JIRAMobileConnectFAQ-HowmuchdoesJIRAMobileConnectcost?
https://developer.atlassian.com/display/JIRADEV/Enabling+JIRA+Mobile+Connect
https://www.youtube.com/watch?v=VlDyjA37rjU - Video explanation to configure JIRA.
PL Crash Reporter (Open Source) :
http://landonf.bikemonkey.org/code/objc/Reliable_Crash_Reporting.20110912.html
http://landonf.bikemonkey.org/code/objc/Reliable_Crash_Reporting.20110912.html
JIRA using the PL Crash Reporter.
Hockey App(3rd party Paid application) :
Features : http://hockeyapp.net/features/
Atlassian Integration : https://developer.atlassian.com/display/JIRADEV/HockeyApp+Third-Party+Integration
Our application use crashlytics to track whenever application crashes.
It helps to improve quality of the application
Should use feedback from your application to allow user feedback

Capturing and sending crash logs to the server

If there is a crash for an application, can I capture the crash logs and send it to a server right after the crash. I guess my question really is if the app crashed can I use the network api to send some data to the server.
Lots of services out there to do this... HockeyApp & TestFlight spring to mind.
Update: HockeyApp has just released a Mac Application 'HockeyCoach' to allow you to view crash reports within a native App, with awesome functionality like viewing the source code referenced in the crash log etc...
I highly reccomend you check it out: http://hockeyapp.net/releases/hockeycoach/
Yes, there are several solutions that provide this functionality. One of them that I'm intimately familiar with (and works very well) is Apigee's Mobile Analytics (http://apigee.com/docs/enterprise/content/analyze_apps).
One of the important points for dealing with crash logs is to save a copy of your .dSYM. This is needed to symbolicate the crash log.
Try using Crashlytics. Extremely simple to incorporate into app and is completely free.

Blackberry crash log collection

Is there a mechanism to collect all the stack traces of a BlackBerry application if I am doing OTA app delivery?
I believe Apple collects and gives us the crash logs, or you can extract them by connecting the iPhone to a dev machine and using XCode to read the crash logs. Is there an equivalent mechanism for the Blackberry?
If not, are there any libraries that can log all the exceptions and push them out to a server?
Automated collection just isn't possible. There's no way to get a stack trace in a String, which would be the first step of an automated crash handler.
There's a StackOverflow question just about getting the stack as a string:
Is there a way to get the stack trace of an exception in form of a String in Blackberry?
If you are doing development and can connect your computer to the device, you can get the event log or console output by using javaloader.exe. JavaLoader has a pretty long help page which it displays if you run it without arguments. You can find JavaLoader.exe in your Eclipse plugins folder, where the BlackBerry JDE is unpacked.
The StackOverflow question that mentions JavaLoader:
Tool to get BlackBerry log
If you really want to ask your users for stack traces, they will appear in the Event Log automatically (at least, for uncaught exceptions). They can use ALT-LGLG from the device home screen (on devices with keyboards) to get into the Event Log, and then from there they can copy the day's events to the clipboard and paste into an email.
The biggest downside to this approach is that the event log is often larger than the clipboard can hold, so you won't get a full event log.

Resources