- JW LIBRARY APP CRASHES WINDOWS 10
- JW LIBRARY APP CRASHES CODE
- JW LIBRARY APP CRASHES LICENSE
The library is licensed under the Apache License 2.0.
This library will not make you toast for breakfast :)Īny contribution in order to make this library better will be welcome!. There is no guarantee that this will work on every device. This will not avoid ANRs from happening. If you test it with such configuration, please provide feedback too! This app gives me all the book love I need when I am away from a real library. While I will take any opportunity to visit a brick and mortar library, it isn’t alway possible. The library has not been tested with multiprocess apps. This app is intuitive, helpful, and like having a librarian in my pocket. If you test it with such configuration, please provide feedback! It uses Class.forName() to load classes, so maybe that could cause some problem in API<21. The library has not been tested with multidex enabled. If your app initialization or error activity crash, there is a possibility of entering an infinite restart loop (this is checked by the library for the most common cases, but could happen in rarer cases). CustomActivityOnCrash will not work with any custom UncaughtExceptionHandler set after initializing the library that does not call back to the original handler. JW LIBRARY APP CRASHES CODE
Look at the code if you need more detail about how it works.
JW LIBRARY APP CRASHES WINDOWS 10
The inner workings are based on ACRA's dialog reporting mode with some minor tweaks. Sometimes an app on Windows 10 just doesn’t want to play nice.
Launches a new intent to the error activity in a new process passing the crash info as an extra. Captures the stack trace that caused the crash. When an exception is caught by the library's UncaughtExceptionHandler it does the following: This library relies on the tDefaultUncaughtExceptionHandler method. No need to add special rules, the library should work even with obfuscation. If in doubt, check the code in that module. The sample project module includes an example of a custom error activity. You MUST call this to close the app, or you will end up having several Application class instances and experience multiprocess issues. closeApplication(activity, eventListener) Ĭloses the app and kills the current process. If you choose to create your own completely custom error activity, you can use these methods:ĬustomActivityOnCrash. There is a sample project module with examples of these overrides. An unexpected error occurred.\nSorry for the inconvenience.
0 kommentar(er)
