What is the impact of many crash reporting tools on Android

Question

In my application, I enabled Crashlytics, ACRA, and Google Analytics to report crashes

-> is there a side effect of one on the other?

-> Which one is better to use.

-> How do crash reporting services work if someone catches a crash, how do others find out about the same crash?

Answer 1

is there a side effect of one on the other?

Google Analytics is not very good to use. I created a Google Analytics account a few days before its implementation. It was not used or even copied (code), and when I returned to paste Google Analytics, I needed to get the code. No one used the version of the Google Analytics application, and it was not even released, and it had many protocols. I don’t like Google analytics because the code is easily hacked and used by third-party sites without the consent to add fake clicks to your site when the code is not even used there.

In addition, Google Analytics only processes on login. Since it is not a special fault analysis tool, it does not record crashes like ACRA, Crashalytics and Firebase crashes.

Which one is better to use.

It really is up to you, but I personally think ACRA is better because you can use the backends on your own site. If the site goes down, just like ACRA, it really helps to feel control over the return of the site.

In addition, there are many backends if you want to use your own website. And if you do not find what works, you can create it. Crashalytics and Firebase rely on their own toolbar on their respective pages, which means remembering another password and username.

How do crash reporting services work if someone catches a crash, how does another get a crash report?

See Drew's answer

Answer 2

Using multiple crash reporting solutions in one project at the same time can lead your application to a concurrency problem, where the application will eventually freeze forever in the event of any failure.

Failure reporting solutions intercept failed failures, one way or another. The stream is basically the same:

• Interception of unsuccessful failure;
• Log in to send information to the server;
• Re-throw crash, so the application will eventually work.

I could imagine a situation where 2 solutions for crash reports create an endless loop throwing the same exception on each other forever, in accordance with the above steps.

At least it was like when I used Google Analytics (with crash reporting enabled ) along with Crashlytics . The app simply hung forever without any apparent glitches, until I ended up turning on the Google Analytics off report .

Answer 3

Crash analytics tools It is possible to use Global Exception Handling , as in this fooobar.com/questions/129142 / ... for the entire application to handle exception exceptions.

SO, if you use several crash analysis tools, each of them can replace the Global Exception handler.