Debug Instructions
1. Logcat File Output
//log configure
//log --- Whether output logcat, it is recommended to open when developing, close when publishing
JL_Log.setLog(BuildConfig.DEBUG);
//log file configure
//context --- Context, the suggestion is getApplicationContext()
//isSaveFile --- Whether save logcat file, it is recommended to open when developing, close when publishing
JL_Log.setIsSaveLogFile(context, BuildConfig.DEBUG);
Note
1. It is recommended to set the printout in the Application
2. Printing is enabled by default for debug versions and disabled by default for release versions
3. Customers can enable or disable debugging in the demo project
2. Logcat File
Logcat File Format
format: ota_log_app_[timestamp].txt
timestamp: timestamp
For example: ota_log_app_20220330093020.432.txt ==> OTA library logcat file, create time: 2022/03/30 09:30:20
File Storage Path
File storage path unified in
./Android/data/[package name]/files/logcat/Package Name: Application package name, Such as: com.jieli.otasdk
For example: ./Android/data/com.jieli.otasdk/files/logcat/
3. Exception Feedback Steps
Important
Prerequisite: Exit APP after abnormal situation
1. Brief description of problem phenomena (necessary)
2. Provide the log file closest to the timestamp (necessary)
3. Briefly describe the time period during which the anomaly occurred
4. Provide screenshots or videos of the phenomenon
4. Test Demo
App Name: JL_OTA
Package Name:
com.jieli.otasdkImportant
1. Do not use the test demo package name on any platform
2. It is not recommended to use test demos for commercial purposes