Caught Exceptions having error object from ANRWatchDog not getting logged on Crashlytics Dashboard about anr-watchdog HOT 10 CLOSED

I contacted Crashlytics support and they stated:

Our limit is around 64kb or 128kb in some cases. It looks like ANRwatchdog is producing reports over 500kb

So looks like currently you must use the setReportMainThreadOnly() option as it limits the size of the report.

from anr-watchdog.

I have been looking into this, and I was able to get this to work by setting the ANRWatchDog to only report the main thread.

anrWatchDog.setReportMainThreadOnly()

I still cannot get this to work without that setting.

from anr-watchdog.

Hi,
We`ve come across exactly the same problem. onAppNotResponding callback is raised, but the issue on crashlytics never created. Any thoughts or updates on this?

from anr-watchdog.

I too was having this issue earlier, it seems when you Log a non-runtime exception in crashlytics it creates nonfatal exceptions in fabric dashboard since ANRs don't necessarily crash an application. You need to toggle the switch in the fabric dashboard to show all exceptions including non-fatals as by default it only shows fatal exceptions.

Another issue might be proguard which when enabled strips some important classes required by anrWatchDog. To prevent that use the following rule in your proguard-rules.pro file.

-keep class com.github.anrwatchdog.** { *; }

You might also want to do the following to change the error into string

  anrWatchDog.setANRListener(new ANRWatchDog.ANRListener() {
            @Override
            public void onAppNotResponding(ANRError error) {
                StringWriter sw = new StringWriter();
                error.printStackTrace(new PrintWriter(sw));
                CrashUtil.logException(new RuntimeException(sw.toString()));
            }
        });

Hope it helps!

from anr-watchdog.

@navaneet Regarding the dashboard thing, I have already selected "All Events".

Will surely look into the 2nd part of your solution though. Thanks!

Btw Fabric team replied that they are receiving an empty report and hence it is not showing in the dashboard. Any thoughts?

from anr-watchdog.

Not sure, however if it logs into logcat it should log into fabric too. Try logging to logcat and then check against fabric if the same error is getting logged.

from anr-watchdog.

I dont think that proguard is the case because weve got the same situation for our debug builds (which arent minimized). But Ill give it a try.
I also tried it with some dummy exception and it works fine. So the problem is definitely with ANRError class

from anr-watchdog.

@mflesh1 I think issue is because of ANR format. Crashlytics is expecting an exception which normally contains a message and a stack trace. When "setReportMainThreadOnly" is disabled, ANRError creates a nested stack trace of all threads which Crashlytics does not accept. If I convert the ANRError into a string, as suggested by @navaneet , then it get posted fine. But then there is error grouping issue on crashlytics dashboard which I am currently trying to figure out. .

from anr-watchdog.

ANRError indeed is too big for Crashlytics. I convert errors into text files and upload to Firebase storage it is free and you can setup it from Android Studio.

from anr-watchdog.

The documentation warns about this.
That's all I can do 😞

from anr-watchdog.