Tag creation fails for short stack traces about timber

[JakeWharton]

How are you calling? There are four method calls inside Timber and the fifth is your callsite.

[jbarr21]

like this...

    (new Thread() {
            @Override
            public void run() {
                try {
                    OrderParams orderParams = new OrderParams(UserAccount.getLoggedInUserId(), purchaseId);
                    ClientApis.getApi().submitOrderNotice(orderParams);
                } catch (RetrofitError re) {
                    Timber.e(re, "Error submitting order notice on product purchase completed");
                }
            }
        }).start();

[jbarr21]

Exception from log...

java.lang.ArrayIndexOutOfBoundsException: length=5; index=5
            at timber.log.Timber$DebugTree.a(Timber.java:255)
            at timber.log.Timber$DebugTree.c(Timber.java:248)
            at timber.log.Timber$1.c(Timber.java:139)
            at timber.log.Timber.c(Timber.java:59)
            at com.clientname.util.ClientNameMediatorImpl$1.run(ClientNameMediatorImpl.java:73)

[edenman]

I can't repro this...even if I log from a thread, I still get this as the top 5 items in the new Throwable()'s stack:

It looks like your stacktrace is obfuscated, maybe proguard is inlining methods/classes in Timber and that's what's causing the stack to be shorter than we expect. Can you try excluding Timber from the proguard config and see if that fixes it?

[jbarr21]

Ah, proguard. Thanks @edenman! That did the trick.