CODEWITHSUNDEEP
androidcrash-reports
Dus
Dus

Reputation: 4240

Crash report for an android library - not to be related to the application iteslf

I'm looking for a crash reporter api, which will work on an sdk that we've been developing, regardless of the app which uses the sdk.

I don't want all the apps that uses our sdk to do any other definitions for this purpose, I want it to be in the background, and not related the the app's gradle, manifest or Application's onCreate method.

I've been searching a lot for this, and all the api i found demanding one of the requirements in the paragraph above.

So, here's a list of sdk that i've looked into, all of them require an app definition, which doesn't fit my needs.

  1. Firebase : Fe, firebase is require to set the gradle dependency in the app level, define the app itself and init the sdk in the application context(which i can handle in the library) : 

    compile 'com.google.firebase:firebase-crash:10.2.0'

  2. Crashlytics

  3. acra
  4. New relic
  5. instabug
  6. apteligent
  7. hockeyapp

Please don't offer something like 'make all the apps that using the sdk define x,y,z' - this is not the solution i'm looking for.

Upvotes: 5

Views: 3239

Answers (1)

Syzygy
Syzygy

Reputation: 608

I don't think there are any libraries that work the way you want.

However what you could do, is to fill all your outwards facing methods with try/catch(Exception e) and handle the logging yourself. E.g. simply by silently sending an email or by some REST call.

Be sure to throw the exceptions again after sending, so that the implementing app can deal with the failure as well and is not left in a state where it thinks what your lib did worked, when it actually failed.

Upvotes: 1

Related Questions