LogcatReporter | Android library that sends the Logcat log

by Ereza Java Version: 1.4.0 License: Apache-2.0

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

kandi X-RAY | LogcatReporter Summary

LogcatReporter is a Java library typically used in Logging applications. LogcatReporter has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub, Maven.

This library sends the Logcat log to Crashlytics when your app crashes. Having more information about a crash is never a bad thing, right?. Yes, you could change all your Log.x() commands to Crashlytics.log(), but that's a waste of time. Also, what about system logs or third-party libraries which you can not change? This library fixes this problem.

Support

Quality

Security

License

Reuse

Support

LogcatReporter has a low active ecosystem.

It has 17 star(s) with 4 fork(s). There are 3 watchers for this library.

It had no major release in the last 12 months.

LogcatReporter has no issues reported. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of LogcatReporter is 1.4.0

Quality

LogcatReporter has 0 bugs and 0 code smells.

Security

LogcatReporter has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

LogcatReporter code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

LogcatReporter is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

LogcatReporter releases are available to install and integrate.

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.

LogcatReporter saves you 76 person hours of effort in developing the same functionality from scratch.

It has 196 lines of code, 7 functions and 12 files.

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

Top functions reviewed by kandi - BETA

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

Install the LogcatReporter
Installs the logcat reporter
Send a logcat to the application
Initializes the activity UI
Record an exception with logcat

Get all kandi verified functions for this library.

LogcatReporter Key Features

No Key Features are available at this moment for LogcatReporter.

LogcatReporter Examples and Code Snippets

No Code Snippets are available at this moment for LogcatReporter.

Community Discussions

Trending Discussions on LogcatReporter

Collect logs from system classes

QUESTION

Collect logs from system classes

Asked 2018-May-07 at 15:41

I'm working on an app that uses Android's MediaMuxer for recording the screen. Using Crashlytics, a significant number of users have the "Failed to stop the muxer" crash, but I can't reproduce it locally on any of my devices. According to another question, the MPEG4Writer logs generated while MediaMuxer is running should indicate what the source of the problem is, but since I'm unable to reproduce it locally, I need to collect those logs remotely and pass them over to Crashlytics.

So here's my problem: MediaMuxer and MPEG4Writer are system classes, so obviously I can't edit them to add Crashlytics.log() lines. I've thought of having the app read the Logcat output and storing all entries containing MPEG4Writer, which are then sent to Crashlytics if the muxer crashes, using this implementation as a base. Here's my code:

...

ANSWER

Answered 2018-May-07 at 15:41

So how am I supposed to collect those logs?

Generally, unless you are working for a device manufacturer, you don't collect those logs.

First, accessing LogCat at runtime has never been officially supported; hence, the clunky "fork logcat" approach that you have to take.

Beyond that, you need the READ_LOGS permission to get more than what you are. That permission has signature|privileged|development for the protectionLevel, meaning that ordinary apps cannot hold that permission.

This is for privacy reasons. READ_LOGS gives you access to all of LogCat, and lots of apps (and some system processes) log information that may be sensitive.

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

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

Vulnerabilities

No vulnerabilities reported

Install LogcatReporter

On your application class, use this snippet:. WARNING! You MUST install LogcatReporter AFTER initializing Crashlytics. If you don't, it will not work.