android-logger | Useful logger for Android

by noveogroup Java Version: 1.3.6 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | android-logger Summary

android-logger is a Java library typically used in Logging applications.,roid-logger has no bugs, it has no vulnerabilities, it has build file available and it has low support. However android-logger has a Non-SPDX License. You can download it from GitHub, Maven.

Useful logger for Android based on standard android.util.Log class. Simple lightweight (< 50 Kb) implementation of SLF4J API. Easy but powerful configuration via properties file and some additional helpful logging methods. Easy analogue of popular log4j library. Android SDK Version: API 7 [ Android 2.1 ].

Support

Quality

Security

License

Reuse

Support

android-logger has a low active ecosystem.

It has 219 star(s) with 47 fork(s). There are 20 watchers for this library.

It had no major release in the last 12 months.

There are 9 open issues and 23 have been closed. On average issues are closed in 78 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of android-logger is 1.3.6

Quality

android-logger has 0 bugs and 0 code smells.

Security

android-logger has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

android-logger code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

android-logger has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

android-logger releases are not available. You will need to build from source code and install.

Deployable package is available in Maven.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

android-logger saves you 684 person hours of effort in developing the same functionality from scratch.

It has 1583 lines of code, 244 functions and 18 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed android-logger and discovered the below as its top functions. This is intended to give you an instant insight into android-logger implemented functionality, and help decide if they suit your requirements.

Logs at DEBUG level
Log a message at debug level
Log at DEBUG level
Perform single parameter substitution before logging the message of level DEBUG
Logs at INFO level
Log a message object at ERROR level
Sends a warning message
Sends a WARN log message
Perform double parameter substitution before logging the message of level ERROR according to the format outlined above
Sends a WARN message
Logs a message at the WARN level
Perform single parameter substitution before logging the message of level WARN according to the format outlined above
Log a message object at WARN level
Perform single parameter substitution before logging the message of level INFO according to the format outlined above
Log a message object at INFO level
Logs a message at the ERROR level
Print a message to the log
Print a log message
Logs a message at the VERBOSE level
Log a message at level TRBOSE
Shortenates a class name
Returns true if trace enabled
Returns true if the log level is enabled
Returns true if the logger is enabled
Returns true if the logging is enabled
Is debug enabled
Checks if messages are enabled
Loads the logger configuration file
Compiles the given pattern string
Checks if messages should be logged or not
Returns whether or not the given log level is enabled

Get all kandi verified functions for this library.

android-logger Key Features

No Key Features are available at this moment for android-logger.

android-logger Examples and Code Snippets

No Code Snippets are available at this moment for android-logger.

Community Discussions

Trending Discussions on android-logger

Running into LinearAlloc overflows midway through integration tests

QUESTION

Running into LinearAlloc overflows midway through integration tests

Asked 2020-Mar-02 at 11:36

This is for a largish 3-4 year running Android project, running on Gradle 5.4.1. Integration testing is with Mockito, espresso and dagger.

I have run into an issue where we are adding a Pendo library to the project, the dependency was added to Gradle as standard. Everything runs fine, until we try to run integration tests (~2000), these are run in shards with Spoon.

Around half way through the integration tests, on random tests each time, we run into a native crash killing the test run, due to LinearAlloc exceeding capacity. Running these tests in isolation, or in their classes locally they pass with no issues and have been stable for a long time.

I brought the whole app back to the known good build, added the Pendo dependency only and this results in the same problem, however I don't believe this is due to Pendo, as I tested by coming back to a known good build (tested on again at this point for sanity) and adding a random new dependency, this resulted in the same problem.

From what I can find this may be something to do with the method limits around Android. I should mention we are using multidex to break the app down. Proguard and minify are also being used.

Part of the issue here is that I'm really not sure what to look at to figure out what's going on to cause this overflow. Following the logs for the test runs, nothing appears to be amiss, bar a fair bit of garbage collection (which I'm guessing means a leak somewhere). I'm unsure if this issue is down to some underlying leak, and the new libraries are pushing something just over the edge, or if there's some dependency limit in android that I'm unaware of, or some other way to break the files down so we aren't causing LinearAlloc to fill up.

From reading, I know the limits of LinearAlloc were upped around Android 5, we are having problems on devices both above (Android 10) and below this (Android 4) and I don't really see much chat around this since 2017, so I feel like I'm missing something obvious, or something is misconfigured in the project given it was setup before then.

Any help would be really appreciated. I've dumped a cut down version of the gradle file below

...

ANSWER

Answered 2020-Mar-02 at 11:36

Okay so this was a fun one, leaving this up incase anyone ever runs into a similar issue.

It seems in this case, the error message we were getting out was fairly misleading. A good way to help diagnose these sort of errors is to look at the tombstone left by the crash, see https://source.android.com/devices/tech/debug/native-crash for more info around that

In this case proguard was our enemy, it seemed to be performing some sort of optimisation on the test code leading to variables being assigned incorrectly and was resolved by adding -optimizations *other optimizations*,!code/allocation/variable this might not work for your particular case, but maybe try configuring proguard to do no optimisation and see if that helps :D

Source https://stackoverflow.com/questions/60420269

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install android-logger

If you want to use Android Logger in your Android application you need to do just the following simple steps:.
Add Android Logger as a library OR add it as Maven or Gradle dependency.
Configure Android Logger.
You need to get logger instance to print messages
You can use Log class to make logging calls shorter.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: