Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Stack Traces on Startup

See original GitHub issue

Short description of the issue Stack traces on startup of the app: NoClassDefFoundError Expected behavior Maybe just logging instead of stack traces? Maybe this is not really a problem. Or maybe it’s just an artifact of how I’ve configured the project? Actual behavior When I started the app for the first time, the Logcat gets lots of NoClassDefFoundError stack traces (see here: https://github.com/sengsational/secure-quick-reliable-login/wiki/Logcat-with-NoClassDefFoundErrors). Steps to reproduce I forked the project, pulled the project into Android Studio 3.3.1, then ran it on my device “Moto G (5) Plus (Android 8.1.0, API 27)”.

Issue Analytics

State:
Created 5 years ago
Comments:6 (5 by maintainers)

Top GitHub Comments

1reaction

sengsationalcommented, Apr 19, 2019

So there were two things causing stack traces in the Logcat on startup 1) Biometric stuff and 2) OnUnhandledKeyEventListener.

I found a solution to 2) here: https://stackoverflow.com/a/42957234/897007

So I moved the biometric stuff out into a separate class again (called it LoginActivityHelper). At first, I tried to put it in the super class (LoginBaseActivity), but when I did that, the stack traces still were happening. Only when it wasn’t in a class that did not extend Activity does it remove the stack trace on startup.

I’ll make a pull request shortly. It should not change the operation of the application at all, but just make it nicer for developers that might come along.

0reactions

sengsationalcommented, May 31, 2019

I’m still not pleased with having stack traces at all, but as I mentioned, I think it’s really Google’s problem to fix; all we could possibly do are the work-arounds that are goofy looking in our code.