How to capture iOS crashes in MonoTouch app

We have input for any .Net Framework exceptions that occur in the iPad MonoTouch app, and we can return them back to our support department to analyze and solve problems.

However, if the application crashes due to an iOS error (i.e. sigsev), we are not sure how to capture this information or tell our very inexperienced users how to get and provide it.

Can anyone offer any recommendations on this?

+4
source share
3 answers

Failures will often (but not always, for example, due to memory) create crash logs on the device. iTunes will download them to user computers.

Do you distribute your application through the appstore? If so, you can get crash logs from it (iTunes will download them).

If not, then the following documents (and sections) about them (and create a procedure for end users to send you crash reports) may be useful.

Xamarin is working to get the Testflight SDK to work fully with MonoTouch (i.e. the service itself (the distribution is already working and integrated into the latest MonoDevelop Releases). This will give you another option (for crash reports) in the future.

+1
source

We use these bindings for the HockeyApp SDK iOS (I believe that they also have Android).
They provide a service similar to TestFlight. The symbolism of automatic failure is very pleasant.

We also use this fix because it is extremely important for the collapse of a journalist working in MonoTouch.
Be warned that TestFlight and HockeyApp are currently crashing your application if you do not use this hotfix.

+3
source

Official (suppose I gave him a mono git mono-vault-hub branch). The monotouch-bindings project on github now supports TestFlight SDK support, check:

https://github.com/mono/monotouch-bindings/tree/master/TestFlight

and

https://github.com/mono/monotouch-bindings

Excerpt from their readme:

Testlight

This is the MonoTouch binding for the TestFlight SDK, which can be found in

https://testflightapp.com/sdk/ 

The current version of this binding for TestFlight SDK 1.2.1 v 1.2.1 was released on December 26, 2012. The bindings were updated on March 17, 2013.

Construction

Run make in the binding directory for the assembly TestFlight.dll

Using TestFlight.dll with your own iOS application

Just add TestFlight.dll to your project. Links in MonoDevelop and you are good to go!

Use the safe TakeOff method. Change TestFlight.TakeOff (token) to TestFlight.TakeOffThreadSafe (token)

+1
source

Source: https://habr.com/ru/post/1379407/


All Articles