Stack Traces on Startup
See original GitHub issueShort 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 Results From Across the Web
Stack Traces in 3 Minutes - Medium
A stack trace is a list of functions called up to the point of an error · Stack trace should be read from...
Read more >How to read google play stacktrace when app crashing on ...
I am quite new to flutter and app development and i find it really hard to make any sense of the stack traces...
Read more >Stack trace in logs at the time of startup - Jira Atlassian
Steps: 1. Setup a new JIRA instance. Result: 1. There is stack trace in logs regarding. 2011-06-10 11:05:20,642 QuartzWorker-1 ...
Read more >Display full stack trace of exception that occurs on startup #5102
I propose the whole stack trace would be displayed in these cases, either on System.err when no logging is configured or on ERROR...
Read more >JS stack trace at startup (#3961) - gnome-shell - GitLab
JS stack trace at startup. The following log occurs reproducibly at startup: JS ERROR: TypeError: method Gio.File.delete_async: At least 3 ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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 extendActivity
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.
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.