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.
Is it possible to redact the crash stacktrace before sending?
See original GitHub issueIssue Description
We have found that some SocketTimeoutExceptions may contain source IP addresses in their messages. Due to the company policy, we need to ensure that no Personal Identifiable Information (PII) is being collected by any of our services or that we block any access to it from our end.
We’ve taken care of redacting error logs and exception stacktraces that would end up in an ACRA report when logging silent exceptions, but I’m wondering if it’s possible to redact the stacktrace of a crash log at all? I’m aware that:
- it’s unlikely we’d let the app crash with a
SocketTimeoutException - unlikely that many other exceptions print out IP addresses in their messages
- the same crash log would end up in Play console, unredacted
But we’d like to take some proactive steps to prove we’re doing anything we can to avoid collecting PII where possible.
Would redacting the crash stacktrace be a case of implementing a Collector extension containing code similar to the StacktraceCollector but just making sure the stacktrace is redacted?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
No need to fork, see https://github.com/ACRA/acra/wiki/Custom-Extensions
Right, that was indeed the problem, I’m getting the
REDACTED_STACK_TRACEfield as expected now, thanks!I’ll try with post processing though, to redact the actual stack trace as you suggested 🙌🏻