secant-android-wallet/docs/testing/manual_testing/Logging.md

# Logging disabled on release builds
1. Create a release build of the app, e.g. `./gradlew assembleRelease`
1. Install the build, e.g. `adb install [path_to_apk]`
1. Start logcat, e.g. `adb logcat`
1. Launch the app
1. Verify that the app does not crash on launch (the app is designed to crash if logs are enabled in release builds)
1. Verify that no logs from the app appear in logcat
[#303] Write crash logs on external storage (#429) - Added automatic exception logging, registered in the Application object - The design sends the exception to a second process, as the main process could be in a bad state when crashing. If we ever encounter problems with this design, it is easily toggleable to turn off with a boolean resource - Reading the process name is a bit complex on older Android versions, so we leverage a ContentProvider (which runs prior to Application.onCreate()) to get the process name - Added a simple logging mechanism for multiprocess and multithread log messages - Refactored spackle-lib into spackle-lib (multiplatform) and spackle-android-lib Co-authored-by: Honza <rychnovsky.honza@gmail.com> 2022-05-31 09:38:02 -07:00			`# Logging disabled on release builds`
			1. Create a release build of the app, e.g. `./gradlew assembleRelease`
			1. Install the build, e.g. `adb install [path_to_apk]`
			1. Start logcat, e.g. `adb logcat`
			`1. Launch the app`
			`1. Verify that the app does not crash on launch (the app is designed to crash if logs are enabled in release builds)`
			`1. Verify that no logs from the app appear in logcat`