Crashlytics deprecating logException() what is the replacement?

Question

Anyone know the replacement call in Crashlytics for logException() which seems to be deprecated as of 2.2.4? My issue is that I have exceptions that I catch, but I suspect they lead to further errors which then cause the application to crash. I want to log all handled exceptions also, and see them in one place. Was using Flurry but just didn't seem to do the trick, where as Crashlytics looks to be more robust. I want them all in the same tool since it is a thousand times easier matching up the exceptions in just one place, rather than patching it together thru LogEntries, Flurry and Crashlytics. Once I get the major crash elements identified I will slowly remove the logException() calls and just look for real hard crashes.

thanks!

Where did u see it's deprecated? From the v2.2.4 [doc](http://docs.fabric.io/javadocs/crashlytics/2.2.4/com/crashlytics/android/Crashlytics.html#logException(java.lang.Throwable)) it doesn't seem to be the case. — Aaron He, Jun 01 '15 at 23:00
Yeah - my thought exactly! But inside of Eclipse it is marking as deprecated (it was not before the 2.2.4 upgrade I did today). But as you state, their documentation does not state that. I can only assume they are deprecating it because it is not supported in IOS? Or they are getting too much traffic? — Stephen McCormick, Jun 01 '15 at 23:22

score 32 · Accepted Answer · answered Jun 03 '15 at 09:20

32

Here it is your : Crashlytics.getInstance().core.logException(e);

answered Jun 03 '15 at 09:20

YenMinh

509
5
12

I think this is the actual answer :) – Wooseong Kim Oct 06 '15 at 04:38
2

Is there any documentation that supports this (not trying to be sceptical, but I'm looking for documentation that will help me solve my bug)? – saltandpepper Jul 14 '16 at 15:43

score 18 · Answer 2 · answered Jun 15 '20 at 00:35

18

After migration from fabric to firebase crashlytics...

FirebaseCrashlytics.getInstance().recordException(e);

answered Jun 15 '20 at 00:35

Tom

6,946
2
47
63

joelreeves · Answer 3 · 2015-06-03T09:23:21.467

8

Crashlytics got updated to 2.3.2. If you look at that documentation it's deprecated. Check out the new exception method here

edited Jun 03 '15 at 09:23

answered Jun 02 '15 at 12:39

joelreeves

1,955
1
18
24

1

Try not to link provide link only answers as links can break or their content change, instead provide the relevant code samples or content directly in your answer and link back to the source. I'll remove the downvote if you update your question – TheIT Jun 13 '16 at 20:34

score 7 · Answer 4 · answered Mar 28 '16 at 16:25

Crashlytics documentation and Fabric.io documentation isn't very clear about this, so just to be clear:

if you are compiling with com.crashlytics.sdk.android:crashlytics:2.2.xxx@aar or older, use this method:

Crashlytics.logException(e);
if you are using com.crashlytics.sdk.android:crashlytics:2.3.xxx@aar, use this method:

Crashlytics.getInstance().core.logException(e);
if you are using com.crashlytics.sdk.android:crashlytics:2.5.xxx@aar, you can use any method:

Crashlytics.getInstance().core.logException(e); CrashlyticsCore.getInstance().logException(e);

Crashlytics.logException(e);

In conlusion: if you wish to rely on the Fabric.io documentation, check to make sure you are not compiling with crashlytics v2.3.xxx

Crashlytics deprecating logException() what is the replacement?

4 Answers4